[Dependent] [CVAT] Relax filtering for overlapping gt skeletons#3358
Merged
Dzeranov merged 1 commit intoMay 21, 2025
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Dzeranov
approved these changes
May 21, 2025
Dzeranov
pushed a commit
that referenced
this pull request
May 21, 2025
* Draw roi point along with bbox in skeleton tasks * Relax filtering for overlapping gt skeletons (#3358)
flopez7
pushed a commit
that referenced
this pull request
May 21, 2025
* Draw roi point along with bbox in skeleton tasks * Relax filtering for overlapping gt skeletons (#3358)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue tracking
Depends on #3356
Context behind the change
During the GT preparation for a
skeletons_from_boxestask, GT skeletons and input RoI boxes are matched between each other so that only unambiguous GT is used for validation. After #3356, we can detect and allow more unambiguous cases, as now annotators have a marker on the requested object. The default ambiguity checks are still needed, but they still can be too cautious, so it can be desired by the requester to customize this matching.object_idannotation attribute. This can be used to forcefully match skeletons and boxes that otherwise would be skipped by the ambiguity detection algorithmHow has this been tested?
Release plan
Potential risks; What to monitor; Rollback plan