next up previous index
Next: User applications Up: Summary of GEANT Previous: Control of physics

Debug and I/O operations

KEY N I VAR Short descriptionCOMMON GINIT
DEBU 3 M IDEMINfirst event to debug./GCFLAG/0
IDEMAXlast event to debug /GCFLAG/0
ITESTprint control frequency/GCFLAG/0
GET 20M LGET NGETnames of data structures tofetch (see Note)/GCLIST/Blank
PRIN 20 M LPRINNPRINuser keywords to print datastructure (see Note)/GCLIST/Blank
RGET 20MLRGETNRGETnames of data structures to fetchfrom RZ files (see Note)/GCRZ/Blank
RSAV 20MLRSAVENRSAVEnames of data structures to savefrom RZ files (see Note)/GCRZ/Blank
SAVE 20MLSAVENSAVEnames of data structures tosave (see Note)/GCLIST/Blank
SWIT 10IISWIT user flags for debug/GCFLAG/0

Note: the user data records for I/O have no effect on the GEANT system, and the user is supposed to analyse them at run time and take corresponding action. For instance, a use of the PRIN data record could be the following:

      CALL GLOOK('VOLU',LPRIN,NPRIN,IPRES)
      IF(IPRES.NE.0) THEN
         CALL GPVOLU(0)
      ENDIF

All the names quoted here are given as 4-character strings in input and their ASCII equivalent is read into the corresponding variable. The same applies to the user lists of the following section.



next up previous index
Next: User applications Up: Summary of GEANT Previous: Control of physics


Janne Saarela
Mon Apr 3 12:46:29 METDST 1995