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

CIFAR-100 Model #26

Closed
shellshock1911 opened this issue Jun 24, 2020 · 2 comments
Closed

CIFAR-100 Model #26

shellshock1911 opened this issue Jun 24, 2020 · 2 comments

Comments

@shellshock1911
Copy link

shellshock1911 commented Jun 24, 2020

In section 4.1 of the paper, you state:

To begin with, we compare FixMatch to various existing methods on the standard CIFAR-10, CIFAR-100, and SVHN benchmarks. As recommended by [31], we reimplemented all existing baselines and performed all experiments using the same codebase. In particular, we use the same network architecture (a Wide ResNet-28-2 [47] with 1.5M parameters) ...

Then in the Appendix, you state:

As mentioned in section 4, we used almost identical hyperparameters of FixMatch on CIFAR-10, CIFAR-100, SVHN and STL-10. Note that we used similar network architectures for these datasets, except that more convolution filters were used for CIFAR-100 to handle larger label space ...

I'm trying to reproduce this particular result, however "more convolution filters" isn't defined in the paper with a number. If my understanding is correct, the codebase is setup so that the default filters for the model is 32, and then you allow users to optionally configure this by passing a --filters argument to the main script. In other words, there's no single source of config files that we can review to understand how CIFAR-100 was treated differently.

Would you be able to provide these implementation details on CIFAR-100?

@david-berthelot
Copy link
Collaborator

Sorry about that, it's --filters=128
Thanks for pointing this out, we'll update the paper to specify that number.

@shellshock1911
Copy link
Author

Thanks! Looking forward to trying it out with this change.

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