Naming conventions

Subroutines starting with u perform general utilities common to CAVEB. Do not use such names for experiment specific stuff. Subroutines starting with e may contain experiment specific code. In most cases they dispatch further routines comprising a second layer of detector specific code. Subroutines starting with f are specific to the 4 experiment. If a second letter is present, they contain detector specific code, e.g. "fp_get_cal" performs the calibration of raw data from the 4 plastic wall.

To avoid confusions, the following abbreviations concerning the second letter have been assigned:

• A for general CAMAC,
• B for the plastic barrel,
• C for the central drift chamber,
• D for the Cerenkov counters,
• E for the event scalers,
• F for the Florence telescope
• G for the GEANT simulation stuff,
• H for the helitron,
• I for the ionization chamber,
• L for laser monitoring
• M for the beam monitor,
• P for the plastic wall,
• R for the rosace setup,
• S for the spill scalers,
• T for TAPS stuff,
• U for user stuff,
• W for multiwire,
• Z for the zero degree counter.

A similar convention is used to ensure unique COMMON block naming:

• /FSTORE/ is the big COMMON used for the initial ZEBRA store,
• /fxFLAG/ denotes a flag COMMON block for detector x,
• /fxLINK/ denotes a ZEBRA link area for detector x.

COMMON block definitions are always kept in INCLUDE files with the same name. In order to reduce the probability of typing errors, the usage of IMPLICIT NONE is strongly recommended.