celeritas::LoopingThreshold Struct Reference

Particle-dependent parameters for killing looping tracks. More...

#include <SimData.hh>

Public Types
using	Energy = units::MevEnergy

Public Member Functions
CELER_FUNCTION	operator bool () const
	Whether the data are assigned.

Public Attributes
size_type	max_subthreshold_steps {10}
size_type	max_steps {100}
Energy	threshold_energy {250}

Detailed Description

Particle-dependent parameters for killing looping tracks.

These threshold values are used to determine when tracks that are flagged as looping (i.e., taking a large number of substeps in the field propagator) should be killed.

In Geant4, tracks are killed immediately if their energy is below the "important energy" (equivalent to threshold_energy here) or after some number of step iterations if their energy is above the threshold.

In Celeritas, the default max_substeps in the field propagator is set to a smaller value than in Geant4. Therefore, an additional parameter max_subthreshold_steps is added to approximate Geant4's policy for killing looping tracks: a track flagged as looping will be killed if its energy is below threshold_energy and it has taken more then max_subthreshold_steps steps, or after max_steps steps if its energy is above the threshold.

---

The documentation for this struct was generated from the following file:

• track/SimData.hh