-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Update Datumaro dependency to 0.2.0 #3813
Conversation
dataset = Dataset.from_extractors(GetCVATDataExtractor( | ||
instance_data=instance_data, include_images=save_images), env=dm_env) | ||
with TemporaryDirectory() as tmp_dir: | ||
dataset.export(tmp_dir, 'datumaro', save_images=save_images) |
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 check if the annotations do not include absolute image paths.
What about the format tests?
Also, think about loading tracks, if all the annotations have a track_id
attribute.
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.
Committed solution for problem with absolute image paths.
The format is tested along with all other formats in files: test_formats.py
, test_rest_api_formats.py
.
About tracks, I have a few thoughts:
- Not to support tracks with Datumaro format until Datumaro as a tool starts to support them.
- Or we can check for
track_id
attribute for all formats in theimport_dm_annotations
function (in other case we'll just duplicate similar code as for MOT format).
How do you think which solution is better?
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.
The second solution looks better to me, but implementing it straight will cause unexpected side-effects. I think, we can try to add a common import option to import tracks, if possible. Not all formats will support this, of course, but those, that do, will utilize it. Not in this PR, though. MOT code is already duplicated with some adjustments in MOTS, btw, so I think the generic variant might be a bit complicated.
|
||
class DeleteImagePath(ItemTransform): | ||
def transform_item(self, item): | ||
if not item.has_image: |
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.
Check 3d tasks too.
Motivation and context
How has this been tested?
Checklist
develop
branch- [ ] I have increased versions of npm packages if it is necessary (cvat-canvas,cvat-core, cvat-data and cvat-ui)
License
Feel free to contact the maintainers if that's a concern.