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 FPEOVF in RootParticleWriter
#2241
fix: Fix FPEOVF in RootParticleWriter
#2241
Conversation
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.
Ok. The alternative would be to wrap all of them into the float
range. I don't think we actually have values that meaningfully exceed float
.
I was not sure why this occurred. Maybe G4 produces a max double in some cases. I will do the float wrapping tho so I do not have to change the reference |
📊 Physics performance monitoring for 950f575Summary VertexingSeedingCKFAmbiguity resolutionTruth tracking (Kalman Filter)Truth tracking (GSF) |
Codecov Report
@@ Coverage Diff @@
## main #2241 +/- ##
=======================================
Coverage 49.35% 49.35%
=======================================
Files 445 445
Lines 25264 25264
Branches 11650 11650
=======================================
Hits 12468 12468
Misses 4512 4512
Partials 8284 8284 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@paulgessinger can you re-approve? |
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.
🚀
I run into a few occasions where `float -> double` caused an FPEOVF. In this PR I change the output precision accordingly. Discovered in acts-project#2232 --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
All our physics monitors depend on the simulation which is not directly monitored at the moment. In this PR I add a first monitoring version for Fatras and Geant4. The monitoring is not optimal yet but should be sufficient if something changes or breaks for simulation. Possible improvements: - record deltas for momenta / eta / phi and so on instead of initial and final Blocked by - #2241 - #2260 - #2262 - #2263 - #2264 - #2265 - #2266
I run into a few occasions where
float -> double
caused an FPEOVF. In this PR I change the output precision accordingly.Discovered in #2232