-
Notifications
You must be signed in to change notification settings - Fork 168
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: python reconstruction trajectory writing #1718
refactor: python reconstruction trajectory writing #1718
Conversation
I'll have to touch this again when |
Codecov Report
@@ Coverage Diff @@
## main #1718 +/- ##
=======================================
Coverage 49.65% 49.65%
=======================================
Files 404 404
Lines 22435 22435
Branches 10258 10258
=======================================
Hits 11141 11141
Misses 4132 4132
Partials 7162 7162 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
📊 Physics performance monitoring for 4eeef8dFull report VertexingSeedingCKFAmbiguity resolutionTruth tracking (Kalman Filter)Truth tracking (GSF) |
I feel like I am breaking the python interface on a weekly basis right now but I don't really see a way around this |
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.
Sorry I think I forgot this somehow, but I let's get this in now.
rearrange writing mechanism for trajectories and reuse it for ambires and others in the future