New eval function of yolov6 #936
Open
Conversation
This file contains hidden or 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
1 participant
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.
When our custom dataset label is not named after the coco dataset file, we are likely to trigger the following bugs when we run the eval script: AssertionError: Results do not correspond to current coco set.
The reasons that trigger this bug are: 1. The eval func could not map the image name to image id; 2. The coco api could not compare the type str with type int.
So we should change the evaluation fucation of yolov6 and the coco api, the corresponding changes of evaluation function is changed in the branch yolov6-eval. In the end, we should add one line of code in coco api after the line of the aforementioned assertionerror like annsImgIds = list(map(int, annsImgIds)).