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 is the test size different from the train size in the self-distill phase ? #18

Open
taintpro98 opened this issue Apr 27, 2021 · 3 comments

Comments

@taintpro98
Copy link

I trained the self-distill phase and found that the train size is (1024, 512) but the test size is (2048, 1024). Fortunately, the mIoU increased. But I felt so confused because of this. Can you explain me this issue ? Thanks !

@krumo
Copy link
Collaborator

krumo commented Apr 28, 2021

This is because different data augmentation is performed. As you can see here, when INPUT_SCALES_TRAIN is provided, the SOURCE_INPUT_SIZE_TRAIN will be explained as crop size on the scaled image. This naming might be a little bit confusing, but I cannot come up with a better way to name these operations. Do you have any suggestions?

@taintpro98
Copy link
Author

But why is the test input size (1024, 512) in source training phase and adversarial phase ? (default) Why didn't you use the same test size with the distillation phase. That made change the performance a lot.

@taintpro98
Copy link
Author

taintpro98 commented Apr 28, 2021

Okay, I found the difference. It's so amazing. But I feel like how you augmented the data is quite reluctant with the scale ratio and the crop ratio and when they were used (source training phase, adversarial phase and distillation phase). Can you show me the connection and the idea what lead you to augmentation ? Thanks !

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