I am encountering a reproducible segmentation fault when enabling collision_track together with photon transport in OpenMC, even for a very small and simple problem. The minimal example (see below in the next comment) consists of a single water‑filled spherical cell with a fixed photon source and low particle/batch counts; the simulation runs correctly if either collision_track is disabled or photon_transport is set to Falseand source.particle is set to ‘neutron’, but segfaults when both are enabled. The crash occurs despite tight collision_track filtering (max_collisions=100, restricted to a single cell) Reducing the number of particles to ~5 sometimes avoids the crash, while increasing to ≥100 particles reliably triggers it. I am using OpenMC 0.15.3 on Linux in an HPC environment with a parallel HDF5 build, running serially (no MPI launch). My questions are:
-
Is
collision_trackexpected to support photon transport? -
Is this a known limitation or bug when using
collision_trackwith parallel HDF5? -
Is
collision_trackintended primarily as a low‑statistics debugging feature rather than for detector‑like photon problems? -
Are there recommended alternatives for identifying photon interaction types or counting energy‑depositing events in photon transport simulations?