Saving and merging Geant4 background¶
Saving background tracks¶
GEMC can save into a file the tracks that produced hits. They can be merged later on with a generator of choice w/o having to run the luminosity beam again .
The option “SAVE_ALL_MOTHERS” can be set to “3” as follows:
This saves all tracks that entered any sensitive volumes into a LUND file. If a track’s mother also produced hits, only the mother is saved so the hits are not double counted .
Merging background tracks¶
The option MERGE_LUND_BG can be used to merge tracks from background file “filename”:
The users can use the internal GEMC generator, cosmic model, or a separate LUND file to generate non-background events.
As an example, three events were run with luminosity background:
event #1 (Figure 1 left) produced no hits,
event #2 (Figure 2 left) produced background hits.
event #3 (Figure 3 left) is a real example of one event with 124,000 beam electrons producing background hits.
The three events, merged to a single track, are shown in Fig 1, 2 and 3 right.
Figure 1. Event 1. Left: no background hits with luminosity. Right: no hits were merged to the generated track.
Figure 2. Event 2. Left: tracks producing hits from luminosity were saved. Right: the tracks were merged to the generated track.
Figure 3. Event 3. Left: tracks producing hits from a realistic luminosity of 124,000 electrons per event were saved. Right: the tracks were merged to the generated track.
The track saved are merged in the event at the time that they were generated by the luminosity beam interactions, depending for example on which beam bunch produced the interation. This ensures that the background is uncorrelated to the generated events.