-
Notifications
You must be signed in to change notification settings - Fork 168
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
refactor: Optional curvilinear state in Propagator #2444
Conversation
So far, without a target surface, the propagator unconditionally produces curvilinear parameters, and allocates a plane surface for this. This adds an argument, which if set to false tells the Propagator not to do that. In particular, we don't use this curvilinear state at all in the CKF and KF (I'm not sure about the GSF).
It isn't used in the GSF either. Rather, the requirement to provide this functionality is a bit annoying (but it should be there I guess) |
Codecov Report
@@ Coverage Diff @@
## main #2444 +/- ##
==========================================
- Coverage 49.71% 49.70% -0.01%
==========================================
Files 461 461
Lines 25989 25990 +1
Branches 11934 11935 +1
==========================================
- Hits 12921 12919 -2
- Misses 4600 4602 +2
- Partials 8468 8469 +1
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
Let's get it in!
So far, without a target surface, the propagator unconditionally produces curvilinear parameters, and allocates a plane surface for this. This adds an argument, which if set to false tells the Propagator not to do that. In particular, we don't use this curvilinear state at all in the CKF and KF (I'm not sure about the GSF).