Despite the name of the feature branch, it doesn't solve the cupy illegal memory issue associated with light.MAX_MC_TRUTH_IDS. I set the light mc association to be off in the configuration file. This truth association gives backtracking information per light readout channel per time tick in the readout window. If we do not know how to use this information downstream, I would think light_dat in the output would be enough to give a sense what segments contribute to the light signals, which it stores the segments yield how many photons to each light readout channel and their arrival times.
For completeness, I updated the light mc association dataset in the output so it is consistent than what it would be before the module-to-module variation change.
Despite the name of the feature branch, it doesn't solve the cupy illegal memory issue associated with light.MAX_MC_TRUTH_IDS. I set the light mc association to be off in the configuration file. This truth association gives backtracking information per light readout channel per time tick in the readout window. If we do not know how to use this information downstream, I would think
light_datin the output would be enough to give a sense what segments contribute to the light signals, which it stores the segments yield how many photons to each light readout channel and their arrival times. For completeness, I updated the light mc association dataset in the output so it is consistent than what it would be before the module-to-module variation change.