Skip to content

Leak of track objects to the next jobs #9860

@AxuJIuyc

Description

@AxuJIuyc

Actions before raising this issue

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

Steps to Reproduce

When annotating objects not with a shape but with a track, there is a leakage of these objects to subsequent tasks.

Example.
Let's create a task with several jobs. If you annotate images from jobs 1 to N, everything is fine. However, if you annotate from N to 1, the annotations break.

  1. You previously annotated all the images in job N.
  2. Then you moved on to annotating job N-1 and left the track objects on the last frame.
  3. Let's go back to job N. Everything is fine in the CVAT UI.
  4. Download the annotations for job N and job N-1 in any format (I tried YOLO Detect and COCO). Everything is fine.
  5. BUT! If we download annotations for an entire task or project, the markup from job N-1 will also be transferred to the images from job N.

If we mark up the entire task from top to bottom, all the tracks left on job M will be transferred to jobs M, M+1, M+2...

Expected Behavior

It was expected that any object, be it a shape or a track, would be limited to its job and would not be moved to neighboring ones.

Possible Solution

No response

Context

No response

Environment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions