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

Fix dimension order in the image shape #542

Merged
merged 1 commit into from
May 8, 2023

Conversation

juliabeliaeva
Copy link
Contributor

@juliabeliaeva juliabeliaeva commented Apr 24, 2023

The order of the dimensions did not matter that much in the 0.5.* version, since it's rarely used. But in 0.6 we use the output shape to create tensors passed to the models, so it's important to have this correct. In quite a few models input width is equal to the input height, but for the Ultraface models these dimensions are different, so the FaceDetectionWithVisualization.kt example will fail in master branch without the fix.

Copy link
Collaborator

@zaleslaw zaleslaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am in doubt about calculations, is it correct?

@juliabeliaeva
Copy link
Contributor Author

I checked once again, everything seems correct to me.

@juliabeliaeva juliabeliaeva merged commit 12659ed into Kotlin:release_0.5 May 8, 2023
@juliabeliaeva juliabeliaeva deleted the image_shape branch May 8, 2023 17:15
@juliabeliaeva juliabeliaeva added this to the 0.5.2 milestone May 8, 2023
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

Successfully merging this pull request may close these issues.

2 participants