Skip to content
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

Reference Kalman filter: tests and development #690

Open
10 tasks
asalzburger opened this issue Aug 27, 2024 · 0 comments
Open
10 tasks

Reference Kalman filter: tests and development #690

asalzburger opened this issue Aug 27, 2024 · 0 comments

Comments

@asalzburger
Copy link
Contributor

asalzburger commented Aug 27, 2024

Follo-up the discussion of the acts-parallelisation meeting from 23/08/204, see https://indico.cern.ch/event/1435327

The proposal is to change the progressive/combinatorial filter (PKF/CKF) for track finding with an (alternative) reference trajectory based track finding (RKF) approach. This should be seen as an alternative implementation of the the current CKF baseline, the latter should still go through the foreseen validation and optimisation.

  • Algorithmic flow of PKF/CKF with mixed navigation + Kalman formalism (not entirely correct, but schematically right):

PKF_Flow

  • Algorithmic flow of RKF track finding:

Reference_Flow

The intention is to break the navigation/propagation loop from the Kalman math and hence have the chance to increase the thread efficiency and reduce desynchronisation. The RKF can thus be seen as two independent tasks of preparing the reference trajectories (a) and then run the Kalman updates (b) - on differences to the reference trajectory.

Strategy

Pre-tests that should enhance our current understanding of thread desynchronisation, this part is largely covered by the already foreseen/planneed KF/CKF optimisation campaign.

  • check if in the current implementation thread efficiency can be improved in case n identical seeds are followed
  • check if in the current KF implementation (refitting mode) thread efficiency can be improved in case n identical tracks are refitted
  • evaluate what degradation is introduced by randomising the tracks successively

(a) Reference trajectory building:

  • Run propagation through the detector and start performance analysis (@beomki-yeo has already started this)
  • Check if the thread efficiency can be improved if identical/similar trajectories are followed in parallel
  • Evaluate and optimise the detray propagation performance
  • If necessary, implement an acceleration structure/material update method with less branching
  • develop a truth based reference trajectory building module to help develop and optimise (b)

(b) Referene Kalman filtering

  • Implement a first prototype for RKF
  • Run on optimal reference trajectories, repeating the tests: identical - similar - random tracks in parallel
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant