Only use one track state per timestamp in (G)OSPA metric #1056
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
In case where there are multiple estimates for timestamp on a track (e.g. multi-sensor fusion), metric should only really be calculated using last state added at that timestamp.
sdhiscocks
requested review from
jswright-dstl and
hpritchett-dstl
and removed request for
a team
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1056 +/- ##
==========================================
- Coverage 94.16% 94.13% -0.03%
==========================================
Files 204 204
Lines 13328 13329 +1
Branches 2723 2723
==========================================
- Hits 12550 12547 -3
- Misses 527 530 +3
- Partials 251 252 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
sdhiscocks
changed the title
jswright-dstl
approved these changes
Jul 3, 2024
hpritchett-dstl
approved these changes
Jul 4, 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.
In case where there are multiple estimates for timestamp on a track (e.g. multi-sensor fusion), metric should only really be calculated using last state added at that timestamp.