-
Notifications
You must be signed in to change notification settings - Fork 187
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
Image size error when training with Swin Backbone and CIFAR datasets #324
Comments
Hey. Thanks for letting us know. I think it's just an issue with the config file. When we moved to omegaconf, we decided to allow the user to have more control of the settings. You should set all backbone kwargs like below (it should also fix your issue):
For reference, this is how we access the kwargs for the backbone: solo-learn/solo/methods/base.py Line 183 in 1aeb6e9
And this is the swin backbone constructor: solo-learn/solo/backbones/swin/swin.py Lines 27 to 37 in 1aeb6e9
Let me know if this fixes your issue and I'll also update the config files :) |
Hi! Thanks for your fast response. I've just tried what you mention but, even if that solves the previous error, it raises a new one:
|
Hmm, can you link the full error? I'll try to check it later. |
Sure! The configuration file is:
And the error is:
Thanks in advance for the help! |
Hey. Sorry but I didn't have time to check it yet. I'll try to do it next week. |
Problem
When I try to run CIFAR datasets with Swin-Tiny Backbone, it return the error:
"AssertionError: Input image height (32) doesn't match model (224)."
Reproducibility
I'm using the following configuration file:
Version used
I'm running the
92ec35f54a507fb5d4edc1dc5723abc022b39eb3
version of the library and this is my environment:Additional comments
I think that on older versions of the library (before the omegaconf update) I could run the Swin Backbone without problems. Also, I believe that, at first, there was a line that changed the window size from 7 to 4 in the case of CIFAR dataset but I can't find it anymore.
The text was updated successfully, but these errors were encountered: