acts-project
bug: large errors in ODD track finding for theta = pi / 2
Together with @andiwand, we noticed that the track finding/fitting in combination with the default seeding gives large errors for tracks that have theta = pi / 2 when using the setup from our physics monitoring.
This can be nicely seen when plotting track errors against truth theta:
The tracks have no time measurements for theta approximately pi/2:
tagging @asalzburger @paulgessinger
We digged a little bit more and it seems plausible that this is due to not having a correct initial time parameter from the seeding. The CKF will then reject measurements with time if they have a big residual which happens by chance. The result is tracks without any pixel measurements and poor IP resolution
I should also mention https://github.com/acts-project/acts/pull/2829 here. There I wire the measurement time through SP and seeds so this effect should go away
This issue/PR has been automatically marked as stale because it has not had recent activity. The stale label will be removed if any interaction occurs.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue/PR has been automatically marked as stale because it has not had recent activity. The stale label will be removed if any interaction occurs.
dev-meeting: @andiwand: this is probably fixed. If time estimation was too stiff, we ould not find a track in the region.
