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

"After using your TLC module, the restored image has a blocking effect. Do you know how to alleviate it?" #16

Open
Redamancy0222 opened this issue Mar 20, 2023 · 4 comments

Comments

@Redamancy0222
Copy link

No description provided.

@achusky
Copy link
Collaborator

achusky commented Mar 26, 2023

Hi, could you please provide more information about your case? For example, which particular model was utilized for which tasks? Also, could you kindly supply an example input and the corresponding restored image?

This will help me a lot to understand the unpleasant results. Thanks.

@Redamancy0222
Copy link
Author

Redamancy0222 commented Mar 27, 2023 via email

@Redamancy0222
Copy link
Author

BaiduYun:https://pan.baidu.com/s/1Xk3SY2h4orkLN4o7sHGKAg?pwd=qdxg
Keyword:qdxg

@achusky
Copy link
Collaborator

achusky commented Mar 28, 2023

Hi, thank you for providing the information.

Regarding your setting, "I set the TLC sizes to 256 and 32," I have a question. Why are there two numbers for the size of TLC? Does it mean $256\times32$? Or do you crop the original input image with size $256\times256$ and use a stride or overlapping size of $32$?

Also, I tested your example inputs with HINet-Local (HINet with our TLC), and I did not find any significant chunking effects in the restored images. Our TLC converts the (global) Instance Normalization in HINet into a local Instance Normalization. You can try HINet-Local in Google Colab. Please let me know if I missed anything.

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