Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

why *= 1.2 for yolo detection result? #43

Closed
YuhaoYeSteve opened this issue Jul 22, 2019 · 3 comments
Closed

why *= 1.2 for yolo detection result? #43

YuhaoYeSteve opened this issue Jul 22, 2019 · 3 comments

Comments

@YuhaoYeSteve
Copy link

Line 40 in demo_yolo3_deepsort.py: bbox_xywh[:,3] *= 1.2. Can I ask why multiply 1.2 for height of yolo detection result?

@ZQPei
Copy link
Owner

ZQPei commented Jul 22, 2019

The detected bbox of pedestrain is not that accurate because the yolo detector is not trained for pedestrain dataset. That lead to the bbox often smaller than it should be. So I multiply bbox's width or height by 1.2 to make the bbox large enough to bound the whole person, which is also helpful to feature extractor in deep sort.

@ZQPei ZQPei closed this as completed Jul 22, 2019
@YuhaoYeSteve
Copy link
Author

got it, thanks!

@czy-orange
Copy link

@ZQPei Hi, I wonder if this is your own idea? I did not see it in original paper or deep_sort tensorflow repo. BTW, do you think it will causes w to be wider than the image width? In my project, I met a problem that sometimes the bbox coordinate is minus. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants