Skip to content

Infrastructure for more bound parameter types #986

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

stephenswat
Copy link
Member

I would like to investigate the addition of different bound parameter type storage methods, like e.g. ones with square root decompositions and UDU decompositions. This will require us to add new bound parameter types (some of which will not have built-in covariance matrices). This commit adds the necessary changes to make this happen, lifting the common parts of the track parameter type into a base type and allowing that to be extended. Code using the bound track parameters are, where necessary, updated to be templated.

I would like to investigate the addition of different bound parameter
type storage methods, like e.g. ones with square root decompositions and
UDU decompositions. This will require us to add new bound parameter
types (some of which will not have built-in covariance matrices). This
commit adds the necessary changes to make this happen, lifting the
common parts of the track parameter type into a base type and allowing
that to be extended. Code using the bound track parameters are, where
necessary, updated to be templated.
@stephenswat stephenswat requested a review from niermann999 May 13, 2025 09:49
@stephenswat stephenswat added the refactor refactoring the current codes label May 13, 2025
Copy link

@stephenswat stephenswat marked this pull request as draft May 13, 2025 11:18
@niermann999
Copy link
Contributor

Why don't we write a covariance type in algebra plugins, which can do the various decompositions, covariance backend storing methods etc (like the transform3 type, but in the generic namspace) and use that in the bound_track_parameter class?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor refactoring the current codes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants