Referees
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 99
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Sorry, dumb question: there's only one classification item, and it's based on crowdhuman at some initial point, so why doesn't it pick up the referee? is that at the backbone/classification (yolox) level or the tracking/MixViT level?
Contributor guide
No contributing guide indexed for this repository
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
The issue provides no file, test, or reproduction steps. Start by tracing how CrowdHuman classification feeds the YOLOX backbone/classification stage and how MixViT tracking handles detections, then reproduce the missing-referee behavior. Done requires an agreed expected behavior and identifying which component drops the referee.
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