next up previous contents
Next: 4.5.4 SUBROUTINE ZAUINI(STEER, MGEOM) Up: 4.5 Patch SGVANA : Previous: 4.5.2 SUBROUTINE ZAORD(MODE, STEER)   Contents


4.5.3 SUBROUTINE ZAINI(STEER, MGEOM) : Analysis Initialisation

Initialises the analysis code.

ARGUMENTS:
INPUT :
    STEER : Steering info. The analysis uses row 4:
                  STEER(4,1)   : How to use the detector hits. In the
                                 example :
                                   1 -> Use perigee parameters (ie. don't
                                        use hits at all)
                                   2 -> Fit track using the right hits.
                                   3 -> Run code to associate hits with
                                        tracks (met 1)
                                   4 -> ditto, met 2.
                         ,2)   : Minimum number of jets to use event
                         ,3)   : 1 -> Make event ntuple
                         ,4)   : 1 -> Make jet ntuple
                         ,5)   : Vertex fit method :
                                   0 -> Start with all tracks, then
                                        exclude tracks until a good vertex
                                        can be made.
                                   1 -> Start with two tracks, then include
                                        tracks until vertex becomes bad.
            In addition the following words are used :
                  STEER(1,2)   : Printing unit
                  STEER(1,3)   : Max number of events to print.
                  STEER(1,4)   : 1.0 -> runs stand-alone, so ZTINI must be
                                 called.
                  STEER(2,4)   : 1.0 -> primary vertex position variations
                                 generated.
                  STEER(3,0)   : Number of different detectors.
                  STEER(3,1)   : Number of layers in the barrel that have
                                 hit information.
                  STEER(3,2)   : Type of information on tracks:
                                   1 -> full track fit result format.
                                   2 -> pxpypz + production points only.
OUTPUT :
    MGEOM : Number of detector geometries.
IMPLICIT INPUTS:
    none.
IMPLICIT OUTPUTS:
    To /ZASTE/ : DOWNUP, vertex-fit method; METHOD, method to use when
      including hits in the track; TYPE, Type of track info; NWNTT,
      Number of words in track ntuple; NWNTJ, Ditto, jet-ntuple;
      LUNPR,  print unit; MAXPR, max number of events to print;
      MINJET, min number of jets to accept event; DST, origin of
      data.
    To /ZADTG/ : NLAY, number of layers with hits generated.
CALLED BY :
ZAPRCS, Analysis PRoCeSsing (see 4.5.1).

CALLED ROUTINE(S):
ZTINI (see 4.4.55)

(To do Tracking Initialisation (if requested))

ZTCRAD (see 4.4.17)

(To get detector Cylinder RADius (if VDANA patchy-sel:ed))

ZTCLEN (see 4.4.18)

(To get detector Cylinder LENgth (if VDANA patchy-sel:ed))

ZTCEZ (see 4.4.23)

(To get detector Cylinder Error in Z (if VDANA patchy-sel:ed))

ZTCERF (see 4.4.22)

(To get detector Cylinder Error in RFi (if VDANA patchy-sel:ed))

VMAX
(CERNLIB routine (if VDANA patch-selected))
ZAUINI (see 4.5.4)

(To let user do private initialisation of analysis)

SIDE EFFECTS:
none.

AUTHORS:
M. Berggren, UFRJ

CREATION DATE:
07-APR-1995


next up previous contents
Next: 4.5.4 SUBROUTINE ZAUINI(STEER, MGEOM) Up: 4.5 Patch SGVANA : Previous: 4.5.2 SUBROUTINE ZAORD(MODE, STEER)   Contents
Mikael Berggren 2003-03-27