-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why not patch? #37
Comments
It's a good idea. Our way is like using 1x1 patches. Using larger patch may reduce the computation cost significantly. However, I haven't tried it yet, because I personally believe low-level problems should keep pixel information. Maybe you can try it and give some feedbacks ~ |
Thank you I will think about it
…------------------ 原始邮件 ------------------
发件人: "JingyunLiang/VRT" ***@***.***>;
发送时间: 2022年6月18日(星期六) 下午4:41
***@***.***>;
***@***.******@***.***>;
主题: Re: [JingyunLiang/VRT] why not patch? (Issue #37)
It's a good idea. Our way is like using 1x1 patches. Using larger patch may reduce the computation cost significantly. However, I haven't tried it yet, because I personally believe low-level problems should keep pixel information. Maybe you can try it and give some feedbacks ~
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why don't you treat patch as a token to embedding but use the channel as the embedding dim
The text was updated successfully, but these errors were encountered: