yolo bbox format #916
Closed
yolo bbox format #916
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned several times in Pull Requests, conversion from
yoloformat toalbumentationsformat and back loses accuracy. This is due to the conversion of coordinates from float to integer and back. Since theyoloformat is already normalized, there is no need to convert anything to integer. I removed the unnecessary conversions and edited one of the tests.I was not able to reproduce this bug on an image of size 100 by 100, so I added tests with images of other sizes that the current version of the library does not pass.