-
Notifications
You must be signed in to change notification settings - Fork 178
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
chore: Adopt physmon plotting ranges #2294
chore: Adopt physmon plotting ranges #2294
Conversation
📊 Physics performance monitoring for e5857a5Summary VertexingSeedingCKFAmbiguity resolutionTruth tracking (Kalman Filter)Truth tracking (GSF) |
Codecov Report
@@ Coverage Diff @@
## main #2294 +/- ##
=======================================
Coverage 49.27% 49.27%
=======================================
Files 450 450
Lines 25408 25408
Branches 11727 11727
=======================================
Hits 12521 12521
Misses 4549 4549
Partials 8338 8338 📣 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.
Hi @andiwand lgtm.
The changes performance label is just caused by the change of the ranges, and not a "real physiscs" change. So I'd say we are good with this
Physmon plotting ranges are not optimal right now. Here I am trying to improve things by properly scaling the axes to what is needed
…roject#2086) Our full chain pulls are in a bad state. Looks like the reconstruction and simulation energy loss did not match up. This PR switches the Fatras interactions on which should bring our pulls back to standard normal distribution. Fixes - acts-project#1643 Blocked by - acts-project#2157 - acts-project#2239 - acts-project#2295 - acts-project#2293 - acts-project#2294
Physmon plotting ranges are not optimal right now. Here I am trying to improve things by properly scaling the axes to what is needed