Skip to content
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 don't use large patch #7

Open
DEAN2012-W opened this issue Jun 26, 2022 · 4 comments
Open

Why don't use large patch #7

DEAN2012-W opened this issue Jun 26, 2022 · 4 comments

Comments

@DEAN2012-W
Copy link

Hello,I have just read your paper,the idea of Inference of the CTformer to overcome the mosaic edge of the patch,.

I have to say it's really a good ides,but I think what about if i set the patch equal to image size((also it's resule in large Flops) alse can overcome this problem.

@wdayang
Copy link
Owner

wdayang commented Jun 26, 2022

Hi @DEAN2012-W, thanks for your interest in your work.

Yes, I agree with you large patch size can solve the mosaic edge problem. However, when the patch size is larger, there will be much greater GPU consumption since self-attention demands more GPU memory in the backpropagation. Even armed with the window attention as proposed in Swin transformer (SwinIR in deonising), a powerful GPU like 3090 can barely handle images of 512*512 with a batch size of 1.

@wdayang
Copy link
Owner

wdayang commented Jun 26, 2022

Also, smaller patch size allows larger batch size for training which indicates more diverse samples and more training stability.
So. we use smaller patch of 64*64.

@DEAN2012-W
Copy link
Author

Thanks,your answer is really helpful for me!

@wdayang
Copy link
Owner

wdayang commented Jun 26, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants