refactor!: Merge curvilinear track params into bound track params #4061
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.
After our last dev meeting we decided that the curvilinear track params are really just bound track params which are constructed in a special way. This PR implements the suggested change and introduces a factory function on the bound track params to construct curvilinear params.
This allows to simplify the propagator interface in the future. The plan is to only accept bound track params as an input and produce bound track params as an output.
--- END COMMIT MESSAGE ---
@osbornjd @paulgessinger @asalzburger
@benjaminhuth this also touches the multi stepper params