-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add options to track to track association algorithm #634
Conversation
Co-authored-by: James Wright <[email protected]>
Co-authored-by: James Wright <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #634 +/- ##
=======================================
Coverage 94.22% 94.23%
=======================================
Files 158 158
Lines 7833 7853 +20
Branches 1506 1513 +7
=======================================
+ Hits 7381 7400 +19
Misses 343 343
- Partials 109 110 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is already an ability to provide mappings to measures, and I think this should be used instead. This changes also removes the ability to provide a custom measure, which may be desirable.
1ccc137
to
0a26364
Compare
I've made some improvements to the track to track association algorithm. The main difference is extra parameters allowing the user to specify whether the entire
StateVector
should be used, or rather just positional elements given in themapping
parameter. The class was also renamed in anticipation of new T2TA algorithms in Stone Soup