-
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
refactor: Material mapping howto for python bindings #1801
refactor: Material mapping howto for python bindings #1801
Conversation
I think it'd be best if @noemina reviews this. |
Codecov Report
@@ Coverage Diff @@
## main #1801 +/- ##
=======================================
Coverage 49.56% 49.56%
=======================================
Files 407 407
Lines 22618 22618
Branches 10316 10316
=======================================
Hits 11211 11211
Misses 4227 4227
Partials 7180 7180 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
📊 Physics performance monitoring for 199537bFull report VertexingSeedingCKFAmbiguity resolutionTruth tracking (Kalman Filter)Truth tracking (GSF) |
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.
just a few points for readability in the docs :)
Doc improvements Co-authored-by: Alexander J. Pfleger <70842573+AJPfleger@users.noreply.github.com>
Hello, it seems pretty straightforward. I only have one comment on the documentation. |
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.
All good to me!
I had to do some minor modification to the doc to pass the CI can someone reapprove ? |
I have been procrastinating on this for way too long. In this PR, I update the material mapping howto to use the python bindings. The relevant bindings have been tested and updated to work as expected. I Also done some update of the plotting script (even if they should probably be phased out) to solve the remaining issue with them.
In the near future I plan to update the material mapping autotuning, once it is done I will update the corresponding doc.
The hashes changes come from the fact the validation vertex spread are now set properly to 0 by default.