-
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
fixed two bug for the GeantinoRecording #276
fixed two bug for the GeantinoRecording #276
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.
Good to go in, as G4 anyway deals with non-const EventActions I don't mind that clear() statement in the retrieval call.
I triggered the rebuild for |
It used to be like that on gitlab but was changed afterward so I just reverted back to that. If we want we could discuss how to change it. |
Codecov Report
@@ Coverage Diff @@
## master #276 +/- ##
==========================================
+ Coverage 44.84% 48.38% +3.53%
==========================================
Files 376 318 -58
Lines 18866 16366 -2500
Branches 8970 7586 -1384
==========================================
- Hits 8461 7918 -543
+ Misses 4905 3180 -1725
+ Partials 5500 5268 -232
Continue to review full report at Codecov.
|
* fixed two bug for the GeantinoRecording * format * format * move the m_materialTracks.clear() into EventAction::clear() * put back the mapper as they where... * put the return back * removed commented line * format Co-authored-by: Moritz Kiehn <[email protected]>
Solved two bug related to Geantino scan.
The first one in RunSimGeantinoRecording.cpp was related to writer being set using a variable hat had already been moved.
The second to the fact that the type written by the EventAction didn't match the one wrtote by the writer. In addition the recorded material where not deleted from one event to the other.