-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
How to reproduce performance in standard models? #735
Comments
@LicharYuan The accuracy of my run is also 39.5. |
@LicharYuan @hhaAndroid Hi, the reported results are trained with batch size 128. We try batch size 64 and get the same results (39.5mAP) as you mentioned. However, the 40.5 mAP can be obtained under batch size 64 when you change the decay factor for the ema model from 0.9998 to 0.9999. Line 166 in 15e8725
We will soon make an official PR. If you want to achieve the reported with batch size 64, try to modify this line. |
@Joker316701882 Thank you! I will try. |
Would you like to upload detailed training settings and logs together with the models? It would be greatly helpful for those who want to reproduce the results. |
@RangiLyu Make sense. We will upload the training log for yolox-s model. The only difference between the setting for this log and the current open-source code is the value of this decay factor (0.9999). |
For now, the training log for training yolox-s is available here: Baidu Cloud: Google Drive: |
Thanks, I will try the decay factor = 0.9999 :). |
@LicharYuan Hi, 0.9998 is the current value. You need to change it to 0.9999 to reproduce our result. |
Thanks for the logs @Joker316701882 can you please confirm that training has been done on 8 Nvidia V100 GPUs ? |
@Joker316701882 Every version of YOLOX has to change 0.9998 to 0.9999? |
@Xielihao Yes. |
Hi, the code I run according to the quick start in
README.md
.However, I get 39.6 mAP which is the performance of legacy models(also showed in paper) .
How to reproduce the 40.5 mAP? Should I update some args?
The text was updated successfully, but these errors were encountered: