-
Notifications
You must be signed in to change notification settings - Fork 137
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
Add MMDetection COCO format importer #1213
Conversation
020bac1
to
66a9f3f
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #1213 +/- ##
===========================================
+ Coverage 80.08% 80.10% +0.02%
===========================================
Files 268 269 +1
Lines 29863 29915 +52
Branches 5845 5850 +5
===========================================
+ Hits 23916 23964 +48
- Misses 4614 4616 +2
- Partials 1333 1335 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. However, I have a feeling that we need to find a way to scale these COCO variants (like Roboflow) at the code level more efficiently. I guess that they have same file contents but different paths.
Thank you for the comment. I agree with you. We might be able to support similar directory structures through small modifications and relaxation. This is same for other famous public formats such as VOC and Cityscapes within mmdetection document https://mmdetection.readthedocs.io/en/latest/user_guides/dataset_prepare.html. Let me think about this more for support kaggle-like datasets in the same codebase. |
Summary
How to test
Checklist
License
Feel free to contact the maintainers if that's a concern.