-
Notifications
You must be signed in to change notification settings - Fork 3.2k
yolo import - use detected sources to search for annotation files #9423
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
Conversation
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.
Please add a test and update the changelog
# Conflicts: # cvat/requirements/base.in # cvat/requirements/base.txt
done. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #9423 +/- ##
===========================================
+ Coverage 73.48% 73.50% +0.02%
===========================================
Files 438 438
Lines 46365 46366 +1
Branches 3938 3938
===========================================
+ Hits 34069 34083 +14
+ Misses 12296 12283 -13
🚀 New features to boost your workflow:
|
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.
Please update the datumaro commit
|
Motivation and context
On Yolo import, importer searches for annotations in the folder where to the archive was uncompressed to get image_info. When the archive is misstructured, e.g. when the folder with dataset was compressed and not just it's content, it works incorrectly.
Using datumaro detection to find actual source folder and search for annotations there.
How has this been tested?
Checklist
develop
branchLicense
Feel free to contact the maintainers if that's a concern.