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

Develop Helix Stepper for Fast Propagation in CKF #852

Open
beomki-yeo opened this issue Oct 5, 2024 · 2 comments
Open

Develop Helix Stepper for Fast Propagation in CKF #852

beomki-yeo opened this issue Oct 5, 2024 · 2 comments
Labels
enhancement New feature or request optimization

Comments

@beomki-yeo
Copy link
Collaborator

beomki-yeo commented Oct 5, 2024

In this talk (Slide 8) of the FTAG workshop, CMS speaker implies that constant magnetic field is used in track finding. We can also follow the same strategy.

In case of using the constant field in the track propagation inside vacuum, we can use the Helix propagation instead of the current RKN stepper. Fortunately, everything we need is included in https://github.com/acts-project/detray/blob/main/core/include/detray/navigation/detail/helix.hpp

@beomki-yeo beomki-yeo added optimization enhancement New feature or request labels Oct 5, 2024
@asalzburger
Copy link
Contributor

Hi @beomki-yeo - this is case dependent, for ATLAS ITk offline chain we are aiming to not refit the tracks after track finding and thus save the time of this; in that case, you want the Runge-Kutta propagator to be used there.

The original ATLAS RungeKutta propagator had a flag to fall back onto single step, which turns it effectively into a helix propagator.
(Actually, in ATLAS we had a fast field and a precise field, one for pattern, one for refit ... not sure if this is still in use).

Having the option to do so, is good, making it the standard not so in my mind.

@beomki-yeo
Copy link
Collaborator Author

I agree that the standard always should be the RKN with an inhomogeneous field.
Helix one is definitely for special cases - I started to think that CMS folks are using the helix propagator for track finding after reading the portability paper you shared recently.
I also think that helix calculation will still be cheaper than RKN even with a single step as the RKN requires calculation at four points.

Time calculation of helix and RKN stepper is going to be the same, so this may not be a big issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request optimization
Projects
None yet
Development

No branches or pull requests

2 participants