tensorflow / tensorflow/models
The bounding box x/y ordering returned by `detect_fn` is unacceptable
Open
Nobody has claimed this yet.
models:research
stat:awaiting model gardener
type:feature
- Dominant language
- Python
- Stars
- 77.7k
- Forks
- 44.8k
- PR merge metrics
- No merged PRs in 30d
Description
For some reason it returns ymin, xmin, ymax, xmax. According to this poll [1] it should at least be xmin, ymin, xmax, ymax, and preferably xmin, xmax, ymin, ymax. I am not sure what maniac chose this ordering because I couldn't find the source after lazily searching for detection_boxes in this repository, but I'd like to see this code to understand what type of person would do this.
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.
Assessment
This issue has not been assessed yet.