tests: data: coco_evaluation: Fix test #5298
Open
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
facebook-github-bot
added
the
CLA Signed
...by deep copying results before passing to coco. The results dictionary will be attached as 'annotations' to the dataset and will be changed, making the use of the same structure impossible for the second time. Previously the test would fail on second call to `coco_api.loadRes()` with an exception (`KeyError: 'precision'` when trying to calculate difference between API results). Also, handle the case when one API produces an exception and the other one does not. Previously, the test code would ignore that and try to calculate the difference. Signed-off-by: Ievgen Popovych <jmennius@gmail.com>
Jmennius
force-pushed
the
fix-test-coco-evaluation-fast-eval
branch
from
e18b231
to
7416833
Compare
Programmer-RD-AI
approved these changes
May 31, 2024
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.
...by deep copying results before passing to coco.
The results dictionary will be attached as 'annotations' to the dataset and will be changed,
making the use of the same structure impossible for the second time.
Previously the test would fail on second call to
coco_api.loadRes()with an exception (KeyError: 'precision'when trying to calculate difference between API results).Also, handle the case when one API produces an exception and the other one does not. Previously, the test code would ignore that and try to calculate the difference resulting in an error.