Open ChristianTackeGSI opened 6 months ago
fairroot/base/sim/FairDetector.cxx (2)
`17-17`: **LGTM!** The code change is approved. --- `97-97`: **Excellent refactoring!** The code change simplifies the `Initialize()` method by replacing the loop that iterated over all sensitive volumes with a single call to `GetRunSim().UpdateSensitiveVolumesForModule(*this)`. This change: - Removes the explicit loop and related variable declarations, making the code more concise and readable. - Delegates the responsibility for updating sensitive volumes to the `GetRunSim()` method, which encapsulates the previous functionality in a more streamlined manner. - Enhances the maintainability of the code by promoting a more modular approach.
@ChristianTackeGSI, can you add an entry in the changelog? For some users that change may be worth mentioning. I have tested the PR with PandaRoot.
@ChristianTackeGSI, can you add an entry in the changelog? For some users that change may be worth mentioning. I have tested the PR with PandaRoot.
fAllSenstiveVolumes
was introduced during a rename for 19.0. So the rename was a breaking change. You correctly identified, that we did not document it properly. So let's document it now: #1555
After the docs have been reviewed and merged (and backported to 19.0), I will rebase this one.
@ChristianTackeGSI, can you add an entry in the changelog? For some users that change may be worth mentioning. I have tested the PR with PandaRoot.
fAllSenstiveVolumes
was introduced during a rename for 19.0. So the rename was a breaking change. You correctly identified, that we did not document it properly. So let's document it now: #1555After the docs have been reviewed and merged (and backported to 19.0), I will rebase this one.
Instead of using a thread local, let's use something that is tied to the "simulaion session" (as noted in some places).
FairRunSim has all the Modules anyway, so let it also have the list of sensitive Volumes.
OR should we move it to
FairMCApplcation
instead?waiting for:
Checklist: