I have written a GEANT4 program to record PMT response to Cherenkov photons emitted from energetic positrons. I have initialized and registered all necessary class in my main function and just for debugging purpose, hardcoded runmanager → BeamOn(1000) in the main function. One weird thing I am noticing is the program is loading some Physics Parameters even after the beginning of Run Action and I am also running into memory issue. The output verbose is as follows:
### === Deexcitation model UAtomDeexcitation is activated for 1 region:
### === Auger flag: 1
### === Ignore cuts flag: 1
9.5
initialize runManager succeed
:::::::::::::::::::Batch Mode Called:::::::::::::::::
:::::::::This is the beginning of Run Action::::::::
=======================================================================
====== Electromagnetic Physics Parameters ========
=======================================================================
LPM effect enabled 1
Enable creation and use of sampling tables 0
Apply cuts on all EM processes 0
Use combined TransportationWithMsc Disabled
Use general process 0
Enable linear polarisation for gamma 0
Enable photoeffect sampling below K-shell 1
Enable sampling of quantum entanglement 0
X-section factor for integral approach 0.8
Min kinetic energy for tables 100 eV
Max kinetic energy for tables 100 TeV
Number of bins per decade of a table 7
Verbose level 1
Verbose level for worker thread 0
Bremsstrahlung energy threshold above which
primary e+- is added to the list of secondary 100 TeV
Bremsstrahlung energy threshold above which primary
muon/hadron is added to the list of secondary 100 TeV
Lowest triplet kinetic energy 1 MeV
Enable sampling of gamma linear polarisation 0
5D gamma conversion model type 0
5D gamma conversion model on isolated ion 0
Livermore data directory epics_2017
After the beginning of Run Action, it reads the Electromag params and Radioactive params as well, although it wasn’t the case for the Geant4 example programs that I tried. What could cause this issue? I would love to have a quick response as it might give me a hint to solve the memory leak issue as well.