-
Notifications
You must be signed in to change notification settings - Fork 541
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 CVAT support for frame_start
, frame_stop
, and frame_step
#3181
Conversation
frame_start
, frame_stop
, and frame_step
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## release/v0.21.1 #3181 +/- ##
====================================================
+ Coverage 15.12% 49.18% +34.06%
====================================================
Files 560 230 -330
Lines 68959 34478 -34481
Branches 597 325 -272
====================================================
+ Hits 10428 16957 +6529
+ Misses 58531 17521 -41010
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@ehofesmann is there a reason you're casting from |
oh I see you just need to use |
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
CVAT has three arguments that let you define which portions of videos are uploaded:
frame_start
,frame_stop
, andframe_step
. This PR adds support to these through keyword arguments when callingdataset.annotate()
with the CVAT backend as well as docs and tests.