Add option to use YOLOv5 AP metric #775
Merged
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 stated in this issue, YOLOv7 uses the AP metric from an earlier version of YOLOv5. The metric has since been updated and according to the developer of v5, this new metric is the same one used by the Detectron2 and MMDetection repositories.
The new v5 metric assumes the maximum recall in the precision-recall curve as 1.0, which results in a higher numeric value than the v7 metric for the same performance. If other repositories use a similar calculation, it may provide a more fair comparison.
Thus, I have added the optional flag
v5-metric
to test using this metric. It can also be used in training for choosing the best model after training.