-
Notifications
You must be signed in to change notification settings - Fork 103
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
Does the setting in this code correspond to Table 1 result on CIFAR ? #9
Comments
Same question. A huge gap between the reproduced and the reported results. |
There is no any difference between the settings in our codes and the settings reported in the paper. I have re-run my experiments on CIFAR-10-IM100 and CIFAR-100-IM100 and achieved even higher results than reported in the paper. |
Now, I use torch1.01 and torchvision 0.2.2_post3 with cuda10.0 and I achieved 78.50% on CIFAR-10-IM100, 42.31% on CIFAR-100-IM100. I think the "Environmental settings" may be the key issue. Thank you for your reply. |
Same question. The enviroment on my server is torch 1.0.1,torchvision 0.2.2.post3 with cuda 10.0.130 and I achieved 82.08% on CIFAR-10-IM50, 46.34% on CIFAR-100-IM50, which are lower than those in your paper.. Thank you for your reply. |
The CUDA nad CUDNN version is 9.0 and 7.1.3 respectively in our experiments. |
Is there anyone solve the reproduced problem? We still cannot solve this problem. |
I use the default cifar10.yaml, cifar100.yaml files with imbalance ratio 100 and train from scatch with this codebase. however, I only get 76.58% on CIFAR10 and 41.56% on CIFAR100, which is far from 79.82% on CIFAR10 and 42.56% on CIFAR100 in the paper. So, if there are any differences between the training setting in this codebase and the training setting corresponding to paper results on CIFAR ?
The text was updated successfully, but these errors were encountered: