Ground-truth bounding boxes included in RPN proposals?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17.9k
- Forks
- 7.3k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 13
Description
Hi,
I am training a Faster-RCNN-like architecture and wanted to log the detection losses on the validation dataset. To obtain these losses, I passed in the targets of the validation data to the forward() method of GeneralizedRCNN. When investigating the results, however, I noticed that each ground-truth bounding box had a near-exact match with a predicted bounding box. When passing targets=None, these bounding boxes were gone. Is this the intended behavior? If so, what is the rationale behind it?
I figured that this line is where the predicted and ground-truth boxes get mixed:
It seems to have something to do with balancing positive/negative sampling. Yet, I don't see how a model would improve from boxes that it did not generate itself.
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
Read torchvision/models/detection/roi_heads.py around line 646 and the GeneralizedRCNN.forward path. Compare proposal generation when targets are supplied versus targets=None, then determine whether the near-matching ground-truth boxes are intentional and what rationale or behavior should be documented or changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100