Skip to content

Fix #228: force parent ID to zero if particle was not created in current sensor volume

Simon Spannagel requested to merge fix_228 into master

This adds an additional check for the creation volume (i.e. the G4Track's vertex logical volume to be the current sensor volume. Before, parent IDs were also present, if the parent particle crossed the sensor, but the daughter was created outside the sensor volume. Now, the daughter particle's parent ID is forced to zero, i.e. being a primary MCParticle to this sensor.

I still have to check if this breaks linking with the respective MCTrack.

This fixes #228 (closed)

Edited by Simon Spannagel

Merge request reports