pyronear / pyronear/pyro-engine
Bug: Bounding box detection is intermittent
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
📌 Description
As shown in the video 📹 (link), the model occasionally misses detections on certain frames, resulting in temporary gaps where no bounding box is displayed. Ideally, the bounding box should persist continuously, even when a detection is missing.
The code responsible for handling this is located here: 🔗 (link). It attempts to interpolate missing bounding boxes using missing_bbox, but this approach is not working as expected.
🎯 Expected Behavior
- If a detection is missing for a given frame, the bounding box should be inferred based on the bounding boxes from neighboring frames.
- Ensure that the bounding box remains visible consistently.
🛠️ Suggested Fix
- Investigate why the current
missing_bboxapproach is failing. - Modify the code to correctly interpolate missing bounding boxes using temporal data from adjacent frames.
- Validate that the fix ensures a continuous bounding box display across the video.
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 in pyroengine/engine.py around line 243 and trace how missing_bbox handles detections across adjacent frames. Reproduce the intermittent gaps using the linked video or an equivalent video, then verify that missing detections are interpolated and bounding boxes remain continuously visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100