Improve the error message when using opt photons as primary #251
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Optical photons' trajectories are not stored in the simulation when using
DefaultTrackingAction
, to avoid creating huge output files. If one wants to save them,OpticalTrackingAction
should be used instead, only for small productions and debugging.On the other hand,
DefaultEventAction
tries to access the trajectory container, to look for the hits associated with every particle and make a cut on the total deposited energy.As a consequence, the combination of
DefaultTrackingAction
andDefaultEventAction
produces a segmentation fault in simulations of optical photons as primary particles, since no other particles are present in the simulation.For the same reason, using
DefaultEventAction
but notDefaultTrackingAction
in standard simulations also causes a segmentation fault.This PR tries to improve the error message to cover these two cases, which are the most common causes of that particular segmentation fault.