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

Result mismatch in cascade-rcnn #8497

Closed
duanduanduanyuchen opened this issue Aug 4, 2022 · 2 comments
Closed

Result mismatch in cascade-rcnn #8497

duanduanduanyuchen opened this issue Aug 4, 2022 · 2 comments
Assignees

Comments

@duanduanduanyuchen
Copy link

I use the config here to train the model and found something unusual. The final bbox_mAP is 35.5 but not 40.3 in the table. Then I found that the default pre-trained weight of r50 has changed in the new version. New pre-trained weights have a higher top-1 acc in classification(76.130%->80.858%) (check here) but caused a worse performance in detection(40.3%->35.5%). When I change the pre-trained weight back to the older one, I finally get 40.3% mAP.

I think the default config should change the link of pre-trained weight to adapt to the new version of torchvision.

Does anyone know the reason why the worse performance was caused by the better pre-trained weights?

@shinya7y
Copy link
Contributor

shinya7y commented Aug 5, 2022

I think the default config should change the link of pre-trained weight to adapt to the new version of torchvision.

The latest mmcv seems to load old weights for backward compatibility.
open-mmlab/mmcv#1867

@duanduanduanyuchen
Copy link
Author

Thanks for letting me know that!

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

3 participants