-
Notifications
You must be signed in to change notification settings - Fork 177
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: Solve the CI issue with the ML solver #2026
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2026 +/- ##
==========================================
+ Coverage 49.82% 49.87% +0.05%
==========================================
Files 420 421 +1
Lines 23955 23898 -57
Branches 10857 10843 -14
==========================================
- Hits 11935 11920 -15
+ Misses 4388 4357 -31
+ Partials 7632 7621 -11 see 12 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
📊 Physics performance monitoring for 2bcdad3Full report VertexingSeedingCKFAmbiguity resolutionTruth tracking (Kalman Filter)Truth tracking (GSF) |
The issue should now be fixed. What was happening was that for the input, I was declaring an Eigen::Array with a size based on the number of tracks in the collection. But the Solver removes the tracks with less measurement than the minimum required, so the size of the Eigen::Array was too large, and the last few elements were just random memory that sometimes was interpreted as nan. The good news is that we were only reading the entry corresponding to the tracks of interest afterwards, so the performance shouldn't be affected (actually, the code should be slightly faster for a larger number of required measurements). |
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.
nice fix!
This ML will try to solve the issue acts-project#2023. Unfortunately I couldn't reproduce that issue on my machine so I have to test it directly on the CI.
This ML will try to solve the issue #2023. Unfortunately I couldn't reproduce that issue on my machine so I have to test it directly on the CI.