Adding support for importing/exporting confidence in YOLO formats #1465
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.
What changes are proposed in this pull request?
YOLOv4 and YOLOv5 import/export with confidence. Issue
How is this patch tested? If it is not, please explain why.
Assert equal detection confidence bounds between base and after export/import.
Updated tests in
tests/unittests/import_export_tests.py
to handle defaultinclude_confidence=False
and non-default
include_confidence=True
cases intest_yolov4_dataset
andtest_yolov5_dataset
Release Notes
Is this a user-facing change that should be mentioned in the release notes?
notes for FiftyOne users.
Set
include_confidence=False
when exporting a dataset in YOLOv4/YOLOv5 formats to include confidence.Importing datasets in YOLOv4/YOLOv5 formats automatically loads confidence if it's present in a txt file with detections.
What areas of FiftyOne does this PR affect?
fiftyone
Python library changes