next up previous contents index
Next: Program flow control cards Up: User control cards Previous: GEANT switches

Events and structures i/o control cards

    The following cards are used to control i/o files and structures to be saved or read:
CDIR 'KEYW' 'directory '                 
CFIL 'KEYW' 'file '                    (space is significant)
SAVE 'KEY1' 'KEY2' ...
RSAV 'KEY1' 'KEY2' ...
GET  'KEY1' 'KEY2' ...
RGET 'KEY1' 'KEY2' ...
By the CDIR   card the user can change the default directory used in the IODB system (IO_DEFAULTS routine). For example the default directory for the detector titles is $SRC/titl/gtit (as from cms113). The user can make cmsim to read the detector titles from a private directory by defining e.g.:
CDIR 'GTIT' '$HOME/public/mygtitdir '  (Divert the default directory)
The CFIL card   is used to provide other than default DB files for the program. The most common CFIL keywords are listed in the following example:
CFIL
     'HBKO'   'hist.hbook '            (HBOOK output file)
     'GTIT'   'trak.tz '               (user trak title file)
     'GTIT'   'ecal.tz '               (user ecal title file)
     'FMAP'   'fmap.tz '               (user field map)
     'PYTC'   'pythia.cards '          (user Pythia control cards)
     'EVBI'   'events.ntpl '           (ntuple kinematics input)
     'FZSI'   'signal_input.fz '       (input signal events file)
     'FZBI'   'pile_input.fz '         (input pile-up events file)
     'EVTO'   'my_evt_out.fz '         (events output file)
     'DETI'   'cms_geom_in.rz '        (input detector description file)
     'DETO'   'cms_geom_out.rz '       (output detector description file)
The keywords 'GTIT', 'EVBI', 'FZSI' and 'FZBI' of CFIL can have multiple definitions implying that several files can be read in one job. The keyword 'EVSI' file name must have the extension 'ntpl'. The 'EVTO' file extension is either 'ntpl' or 'fz' depending on the file type. The 'FZSI' and 'FZBI' file name extension must be 'fz'.

The cards SAVE, RSAV, GET and RGET are standard GEANT control cards and they         are used to control the structures (events) i/o in FZ (SAVE/GET) or RZ (RGET/RSAV) format.

SAVE/GET take the standard GEANT structure names as arguments like 'KINE', 'VERT', 'HITS' and 'DIGI'. Also non-standard GEANT structure identifiers like 'RHIT' and 'RECO' are valid arguments. The keyword 'TRIG'   implies all strucures.

The RSAV/RGET control card is used to save/retrieve detector description structures like 'VOLU' etc. on an rz file defined by the CFIL keywords 'DETO'/'DETI', respectively. The keyword 'INIT' has a special meaning: by it one saves/retrieves the full detector description on/from an *.rz file.

The control cards GET and RGET are also affecting the program flow: If a structure is requested from the input file, the processing request by the corresponding program control card will be overridden.

Notice that when one runs CMSIM without GEANT tracking, i.e. reading HITS etc. structures from a file, one has to remove or comment the KINE control card (add C and blank).


next up previous contents index
Next: Program flow control cards Up: User control cards Previous: GEANT switches

Cms Computing
Mon Apr 27 02:30:35 MET DST 1998