subEventTimeDelay & maxTargetStepSize

System : Linux
REST version : v2.2.10

Hello,
I’m confused about two parameters in TRestG4Metadata.

<parameter name="maxTargetStepSize" value="3000" units="um" />
<parameter name="subEventTimeDelay" value="0" units="us" />

Firstly, what’s the meaning of the subEventTimeDelay? It seems to set
TrackSubeventID. if I set it 0 what will happen?

And I found when I set maxTargetStepSize == 3mm, the gap between hits is not necessarily 3mm.

Thank you.

Hi Mebius, thanks for your question,

actually those parameters have very different purposes.

The first parameter, maxTargetStepSize, should guarantee that 2 hits are not separated by more than 3mm, however, I believe, this is only valid for electrons. Do you get a step larger than 3mm, for electrons?

The second parameter, subEventTimeDelay is a parameter that allows to split a single Geant4 generated event into independent subEvents that are finally treated as an event itself.

For example, if I simulate an event decay from a full chain, I will simulate all the decays in that chain. However, between event and event there will be a period of time, that might be even years.

If the time between two physical interactions in Geant4 is more/higher than subEventTimeDelay, then the hits/deposits will be considered to be in independent subevents.

A reasonable value to introduce as subEventTimeDelay is the total drift time of the TPC.

This will split, for example, a full chain decay simulation, into independent subEvents. It might happen then that you simulate 1000 events, and end up with a larger number of events in the final file because few events were split into subEvents.