The print/debug event range, the specific systems to be debugged and GEANT (bank) structures to be printed can be controlled by the following data cards:
DEBU IFIRST ILAST IDELTA (Events to debug/print) DBUG 'KEY1' N1 'KEY2' N2 ... (Subsystems and levels to debug) HBOOK 'KEY1' N1 'KEY2' N2 ... (Subsystems to invoke HBOOK) PRIN 'BNK1' 'BNK2' ... (Structures to print) SWIT N1 N2 N3 N4 ... N10 (Switches in interact. job)Notice that the DEBU parameters control over the DBUG, PRIN and SWIT flags and they should become ineffective outside the event range determined by the DEBU card. If IDELTA=0 one should have no debug prints for IEVENT>ILAST (if the programmers did it right). If IDELTA>0 one gets just one line per event (event/run number and the random seeds) even for IEVENT>ILAST.
The DBUG card controls sub-detector specific debugs. For instance the control card DBUG 'TRAK' 3 'MUON' 0 sets the tracker debug level to 3 and no debug from the muon system.
Only the first four characters of the FF-keys are significant so that HBOO and HBOOK are equivalent on input card. The HBOOK FF-card is used to control histograms and plots as well as ntuples.
The valid keywords for DBUG and HBOOK card are those defined in the SETUp titles (see section 3.5.1): TRAK, ECAL, HCAL etc including their sub-detectors like MSGC, PXLX etc. The user can check how the flags went by putting the first parameter of the DEBU card to -1 so that one gets the printout of the flags for all keywords.
The flags are propagated to lower levels in hierarchy so that using e.g. the global definition DBUG 'CMSE' 1 puts the flag to 1 for all detectors.