Trajectories crash with GDML

[untitled-angoose]

BDSimGDMLCrash.zip

Running a GDML with the option storeTrajectory=1 active causes a map::at exception which ends the run.
(Exception is on line 494 of BDSEventAction.cc in BDSEventAction::IdentifyTrajectoriesForStorage as it attempts to fill the depth map)

Zip contains a GDML file for which the issue appears, and a GMAD that loads it.

[lnevay]

Hello,

In your input file you do not have any trajectory options enabled. Please can you paste here the exact options you use. Also, can you tell me the exact version of the code you are using or the path if it's from CVMFS.

Thanks,
Laurie

[untitled-angoose]

Hi Laurie,

Unfortunately the crash appears to happen regardless of the trajectory options I have enabled! Just asking BDSim to store the trajectories is enough to cause the crash for me.

I updated my code to the most recent version from the develop branch today, but the crash still occurs.

Thanks,
Angus

[untitled-angoose]

BDSimGDMLCrash.zip

Update on this issue with slight changes to the gmad file, and some further details:

• BDSim Version (Commit): 174072d
• Geant4 Version: 11.2.2
• ROOT version: 6.32.06
• System: Ubuntu 24.04.3 LTS, via WSL2

Trajectory options don't appear to affect the crash - simply turning them on can cause the issue.
In some simulations the crash happens at random (I'm not exactly sure why this is).
However, when I run the attached gmad file with the above software versions on my machine, the crash always occurs on the first event.

Hope this is helpful!

Thanks,
Angus