You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can follow the idea suggested in acts-project/acts#2037. We simply set the target surface where we want to estimate the track parameters and extrapolate the seeds. This will resolve the issue from acts-project/acts#1895 as well.
I would like to make sure that the target surface does not have to be fixed to the perigee surface at vertex but can be arbitrary.
The text was updated successfully, but these errors were encountered:
There are some ongoing discussions on refactoring track parameter estimation in ACTS Core side:
Relevant issues:
Estimate Track Parameters from Seeds use only one surface. What about strips? acts#1895
Current track parameter estimation algorithm can not get the bound track parameters when the seed is defined at strip side. (For strip, seeds locate between two strip modules so they are not bound to the surface technically)
Track parameter estimation algorithm return parameter on the first seed SP surface acts#2037
Estimating the track parameter near the vertex by extrapolating the seed backwardly.
We can follow the idea suggested in acts-project/acts#2037. We simply set the target surface where we want to estimate the track parameters and extrapolate the seeds. This will resolve the issue from acts-project/acts#1895 as well.
I would like to make sure that the target surface does not have to be fixed to the perigee surface at vertex but can be arbitrary.
The text was updated successfully, but these errors were encountered: