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

Custom model gives bad bounding boxes #36

Open
Kanyade opened this issue Sep 4, 2021 · 1 comment
Open

Custom model gives bad bounding boxes #36

Kanyade opened this issue Sep 4, 2021 · 1 comment

Comments

@Kanyade
Copy link

Kanyade commented Sep 4, 2021

Greetings!

I tried running this project with my custom model and it seems to work somewhat fine, it detects the objects (2 classes) but it does not show bounding boxes on my mobile.

The reason is that it gives irrealistic width, height values for the object which cannot be seen on the mobile screen(2220x1080) as seen in the picture below:

image

The original model seems to work fine:

image

This is the part where I added the debug messages in PhoneARCamera:

image

Another thing that bugs me is that the position values are negative with my custom model but it still places the anchor to the object in real life, so it can certainly detect it, but something is off. Any idea why this might be?

@jgcbrouns
Copy link

Have you tried checking your custom anchors that you generated and correctly importing these for inference?

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

2 participants