-
Notifications
You must be signed in to change notification settings - Fork 174
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!: Return all track states from Core CKF #3391
refactor!: Return all track states from Core CKF #3391
Conversation
Discussed this briefly with @noemina - Potentially this should rather be a flag and this flag also toggles if we store anything before the first measurement. In this case we can also store holes at the end of the track. |
…-keep-outliers-material-end-of-track
…-keep-outliers-material-end-of-track
…-keep-outliers-material-end-of-track
I have checked #3644, #3648, and #3391 (this PR) and compared against
where the CPU time is just for I think this shows that the tracking performance changes come from #3644, while #3648 improves the speed slightly. #3391 includes the changes from the other two, but doesn't have any additional effect on CPU or performance. |
Currently CKF tracks can have outliers at the back because the measurement flag is also set for outliers as they contains such information. An additional check is introduced to reject outliers. This is an attempt to also understand the output changes of #3391 better
…e CKF (#3648) Currently CKF tracks can have material states before any measurement was found. This is not true for outliers and holes. The logic is reworked so material, outliers and holes are handled in the same way if we have not found any measurements yet. This is an attempt to also understand the output changes of #3391 better
…-keep-outliers-material-end-of-track
@timadye the physmon diff disappeared now |
…-keep-outliers-material-end-of-track
Quality Gate passedIssues Measures |
Since the Core CKF is growing into its own components which is then absorbed by a track finding algorithm it also allows us to extend tracks into different regions of the detector. While extending tracks we map want to keep eventual holes/material/outliers states at the end or beginning of the track. For this reason the CKF is modified to return all the states it found.
For convenience of the user I added helper functions which allow to trim tracks. This is then exercised in the Examples track finding.
blocked by