The best way to show the interplay between ARTE and HBGEAN is to show
the program tree with the relevant calls.
- ATMAIN
- main program of arte
- ATINIT
- initialisation of ARTE
- HGVERS
- gives out the HBGEAN version number;
- HGKUIP
- defines the interactive (HB)GEAN commands;
- GINIT
- sets default values for GEANT variables;
- HGCONS
- sets default values for HBGEAN variables;
- ATEXEC
- KUEXEC
- executes the ARTE kumac file;
- KAGEAN
- activates HBGEAN and sets GEANINIT =1;
- HGINIT
- initialization:
- GPART
- sets up the GEANT particle code;
- GEOMAIN
- main program of the geometry package;
- MEDMAIN
- gets the material constants;
- xxxGEO
- geometry routines for subdetector xxx
- GPHYSI
- initializes the physical processes for tracing;
- ATEVNT
- initializes event handling via QNEXT(E)
- USINIT
- user routine before event processing,
for instance for HBOOK-plot booking;
- QNEXT
- loop over events;
- ALEVNT/PHEVNT
- call for event generators (LUND/PHASE SPACE);
- USEVNT
- user event routine;
- HGEVNT
- event tracing (called if GEANINIT=1);
- HGKINE
- set up of event kinematic from generator input;
- GTRIG
- GEANT routine for tracing;
- GUSTEP
- standard routine to react in every tracing step;
- GUOUT
- GEANT routine at the end of every event;
- ATSTOP
GEANT will only be activated if the command GEAN is inside the .kumac
file - this command is equivalent to a call to KAGEAN.
From the flow follows that GEANT input command in the ARTE kumac file
which control the physical processes or the geometry implementation
must be given in before the activation of GEANT (command GEAN).
Siegmund Nowak: 2000-04-27