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

Hard coded resolution in video.py and detect.py lead to wrong bounding boxes #43

Open
Oleffa opened this issue Apr 13, 2019 · 0 comments

Comments

@Oleffa
Copy link

Oleffa commented Apr 13, 2019

Hi,

first of all thanks for the great tutorial!

I think in video.py, line 134 and detect.py, lin 164:
scaling_factor = torch.min(416/im_dim,1)[0].view(-1,1)
is using a hard coded value for the image resolution (See standard value for the resolution parameter).

When I was using this implementation with my own yolov3 net the bounding boxes were not drawn in the proper locations since i set the parameter for resolution to 960.

Changing the lines to:
scaling_factor = torch.min(int(args.reso)/im_dim,1)[0].view(-1,1)
solved the problem for me.

Best Regards,

Oliver

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

1 participant