Skip to content
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

Total duration of zoom, change attributes and resize events #7994

Open
2 tasks done
mmoyano-sigmacognition opened this issue Jun 6, 2024 · 3 comments
Open
2 tasks done
Labels
enhancement New feature or request

Comments

@mmoyano-sigmacognition
Copy link

mmoyano-sigmacognition commented Jun 6, 2024

Actions before raising this issue

  • I searched the existing issues and did not find anything similar.
  • I read/searched the docs

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.

excel1
excel2

Are both behavours expected to be this way? Otherwise, is it planned to be fixed in next releases?

Thanks in advance. Cheers,
Manuel

@mmoyano-sigmacognition mmoyano-sigmacognition added the enhancement New feature or request label Jun 6, 2024
@bsekachev
Copy link
Member

I recently documented how working time calculated, please read here: https://docs.cvat.ai/docs/administration/advanced/analytics/#working-time-calculation

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.

@mmoyano-sigmacognition
Copy link
Author

Hi @bsekachev,

Thanks for the quick response. Would it make sense to include the duration of such events in next releases?

@bsekachev
Copy link
Member

Yep, it makes sense, but that is not a priority.
Anybody is welcome to contribute :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants