-
Notifications
You must be signed in to change notification settings - Fork 525
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
[Algorithm] Support Rotated YOLOX (CVPR'21) #409
base: dev
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #409 +/- ##
==========================================
- Coverage 29.46% 28.63% -0.84%
==========================================
Files 121 124 +3
Lines 8495 9032 +537
Branches 1289 1356 +67
==========================================
+ Hits 2503 2586 +83
- Misses 5891 6345 +454
Partials 101 101
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@liuyanyi Thanks for your contribution. May I ask where are the codes of custom_hooks? |
The code for the hooks are in mmdet. |
Thanks a lot. |
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Add Rotated YOLOX
Modification
Add
PseudoAngleCoder
for fake angle coder.Modify
CSLCoder
to support batch decode.Add check in
RotatedIoULoss
.Results:
The first version result shows below, there may be overfitting, ap50 of trainval got 89.63 in 300 epoch.
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist