-
Notifications
You must be signed in to change notification settings - Fork 176
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
fix: Fix vertexing for physmon ckf tracking #2547
fix: Fix vertexing for physmon ckf tracking #2547
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2547 +/- ##
=======================================
Coverage 49.76% 49.76%
=======================================
Files 466 466
Lines 26326 26326
Branches 12097 12097
=======================================
Hits 13101 13101
Misses 4624 4624
Partials 8601 8601 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this conflicting with the name of the physmon procedure truth_estimated/truth_smeared? Or am I missing something?
that refers to the seeder not the track finding |
Invalidated by push of 3f4f80a
Currently our Fatras simulation does not remember the surface particles were created on. This is a problem for the navigation as we cannot know if a close by surface was already encountered or not. I propose to add a reference surface to the Fatras `Particle` which can be carried through in the propagation and then be used as a starting point for a new propagation. We will also have to decide if a photon conversion on a sensitive surface should result in a hit or not. But this should be done in a separate PR if possible. blocked by - #2547 - #2549
associatedParticles
should not be used after CKF as we cannot guarantee that they will line up with tracks coming from the CKF. this way the writer will try to associate the particles via tracks itself.