-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
correct_yolo_boxes #352
Comments
good point. Also It is a bit different from the original implementation It may be related to #338 looks lie another bug introduced while taking this implementation to ImageAI, maybe @OlafenwaMoses can help us to understand this |
the following message was originally posted on #353 but the issue was closed as the main point on the issue was solved. However the message contain some clues to the current #352 issue, which wasn't solved yet I found that Up to this point, my guess is that maybe, the implementation on |
any news on this @OlafenwaMoses @plenari ? |
@rola93 , hi, did you ever figure out how to get around this? |
saddle, nope. However, someone closed the issu, and in addition to this, there is a new ImageAI version, so need to check if it is still there. May be @OlafenwaMoses has some news on this. |
Detetion.custom.init.CustomDetectionUtils.correct_yolo_boxes
hello, I'm confused. Isn't net_w equal to new_w here, so x_sacle is always equal to 1? In my opinion, when using kmeans to generate anchors boxes, you can directly zoom the image to 416*416. Can you also directly zoom back anchors boxes according to the size of the original image? So I don't know how x_offset works? Thanks very much?
The text was updated successfully, but these errors were encountered: