You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm working with CVAT 2.14.0, I've labeled some images using zoom, changing attributes and resizing some polygons. When I checked the events in analytics, I saw that the duration column of those events was set to 0. I can get an approximation with the working_time field in the payload, but the time of those events may be distorted if I don't label in less than 100 seconds, as the difference between timestamps is computed and not the duration itself. In the case of not labeling for more than 100 seconds, the working_time is also set to 0.
Are both behavours expected to be this way? Otherwise, is it planned to be fixed in next releases?
Thanks in advance. Cheers,
Manuel
The text was updated successfully, but these errors were encountered:
Briefly speaking, duration of zoom and resize are not considered at all.
The only difference is that in v2.14.0 working_time appended to the following event payload.
Starting from v2.14.1 we have a dedicated event to store working time.
Actions before raising this issue
Is your feature request related to a problem? Please describe.
I'm working with CVAT 2.14.0, I've labeled some images using zoom, changing attributes and resizing some polygons. When I checked the events in analytics, I saw that the duration column of those events was set to 0. I can get an approximation with the
working_time
field in the payload, but the time of those events may be distorted if I don't label in less than 100 seconds, as the difference between timestamps is computed and not the duration itself. In the case of not labeling for more than 100 seconds, theworking_time
is also set to 0.Are both behavours expected to be this way? Otherwise, is it planned to be fixed in next releases?
Thanks in advance. Cheers,
Manuel
The text was updated successfully, but these errors were encountered: