Empty `sv.Detections` in workflows lack metadata
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 319
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 133
Description
Search before asking
- I have searched the Inference issues and found no similar bug report.
Bug
There is known problem with using sv.Detections in workflows - namely when there is no bounding boxes detected we
cannot set additional metadata.
This is linked to https://github.com/roboflow/supervision/issues/1226 which must be solved first.
Please report issues induced by the problem in the thread below.
Environment
No response
Minimal Reproducible Example
No response
Additional
No response
Are you willing to submit a PR?
- Yes I'd like to help by submitting a PR!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked supervision issue #1226, which the report identifies as a prerequisite, then inspect how empty sv.Detections values are handled in workflows. Done means additional metadata can be set and retained when no bounding boxes are detected, with the induced workflow issues covered by verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100