-
Notifications
You must be signed in to change notification settings - Fork 157
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: ITk full chain #1642
fix: ITk full chain #1642
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1642 +/- ##
=======================================
Coverage 48.58% 48.58%
=======================================
Files 381 381
Lines 20833 20833
Branches 9557 9557
=======================================
Hits 10122 10122
Misses 4108 4108
Partials 6603 6603 📣 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.
Looks good to me.
I tested this with ttbar_pu200=False
and True
and it seems to work nicely.
I see there's now a performance_ambi.root
(just running CKFPerformanceWriter
again). Nice!
yes @paulgessinger suggested to have an output to monitor this. I thought it might be easiest to reuse the |
📊 Physics performance monitoring for e4f5867Full report VertexingCKFAmbiguity resolutionTruth tracking |
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.
lgtm
addCKFTracks
andaddVertexFitting