next up previous contents
Next: A.7 SCAN steering example Up: A. Examples of steering-files Previous: A.5 EXTREAD steering example   Contents


A.6 SINGPART steering example

LIST

C
C In this example, all keys know by default by SGV are shown.
C The commented value is the default.

C ========== General steerings : ============


C  Max # of events
C
C         MAXEV 1000

C  Max # of events to list
C
C         MAXPR 1


C  Unit to list events on
C
C         LUNPR 6

C          Starting seed for detector simulation random number generator.
C          On VMS, setting ISEED to 0 yields new seeds
C          each run (the seed will be calculated from the
C          wall-clock
C
C         DSEED 123345678

C          Starting seed for Lund evet generator random number generator.
C          Same comment. Note that other generators might or might not
C          care about this value...
C
C         GSEED 19780503

C  Save random-number generator seeds on file ( to be able to
C  restart after a crash. Only the most current set will be saved)
C
C         SEED_BACKUP TRUE

C  Frequency of seed-backups. Don't put it much less than this default:
C  I/O take time !!!
C
C         BACKUP_FREQ  100

C  Should the analysing code do initialisation ? (normally not, but if
C  You saved simulated events on a file and are reading them back, it
C  should.
C
C         NEED_ANA_INI  FALSE

C  Skip the event and continue with next on errors (TRUE) or stop
C  execution ?
C
C         SKIP TRUE

C  Should histograms read in be updated (1) or reset (0) ?
C
C         UPDF 1

C  Use column-wise ntuples ?
C
C         CWN FALSE

C  Use any HBOOK external file at all ?
C
C         USE_HBOOK TRUE

C  I/O generated and simulated events :
C           RZ   : output to RZ file
C           FZUT : output to FZ file
C           FZIN : input from FZ file
C           NO   : No I/O (normally what You want)
C  (if 'FZIN' is selected NEED_ANA_INI is set to TRUE)
C
C         IOMODE 'NO  '


C========= Event generator steering ======

C   particle type as JETSET codes : e:11, mu:133, pi:211 etc.
C
C KPART 11

C   Scan ranges. Note that ony one of the three variables
C   can be varied at a time.

C   Range in momentum (PMIN =-1 -> same as max, ie. fixed momentum=PMAX)

C PMIN -1.0
C PMAX 10.0
 PMIN 1.0
 PMAX 100.0

C   Range in theta (THMIN =-1 -> same as max, ie. fixed theta=THMAX)

C THMIN -1.0
C THMAX 45.0
 THMIN 10.0
 THMAX 89.0

C   Range in phi (PHMIN =-1 -> same as max, ie. fixed phi=PHMAX)

C PHMIN -1.0
C PHMAX 0.0

C Average interaction point
C
C    MEAN_VERTEX 0.0 0.0 0.0

C Beam-spot size
C
C   VERTEX_SPREAD   0.015 0.0010 1.000

C Simulate interaction point ? (by default it will be a 0,0,0)
C
C   PRIMARY_VERTEX_SIM FALSE



C========= Detector simulation steering ======

C  Generate hits or track parameters at perigee
C
C         VDHITS FALSE

C  If hits to be generated : In how many layers (not counting the beam-pipe)
C
C         VDLAYS 1

C  Make full set of track parameters with Error matrix, or just
C  3-momentum and production vertex ? If You write the event
C  to a file, putting MTKR to FALSE might be interesting: The size
C  of the file is much reduced. The parameters can the be reconstructed
C  by the analysing code. If You're not writing events out, putting
C  MTKR = false is just a waste of CPU-cycles (the same thing will be
C  done both in the simulation and the analysis)
C
C         MTKR TRUE

C  Number of detectors (MAX=3)
C
C         NDETS  1


C  Generate showers in calorimeters also for charged
C  particles (else only for neutrals).
C
C         CHSHOW TRUE

C          Generate brems and photon conversions in the detector
C          material
C        GENBC  FALSE

C          Minimum electron momentum to generate brems.
C        PMINBR  0.3

C          Minimum photon momentum to generate pair-production.
C        PMINPA  0.0

C          Minimum fraction of pt after to pt before the brems for the
C          original electron to be kept for the tracking
C        PTLOSLIM  0.9

C          Send particles with these codes to analysis
C          By default, all particles with non-zero lifetime
C          are sent and need not be specified here.
C          Use the LUND partcle codes.

C        SAVE_PARTICLES


C          Print the geometry of the dectector after loading.
C         PRDET FALSE

C          Print the geometry of the dectector after loading, in a
C          way usefull for displaying the detector with SHOWDET.KUMAC
C          (if true, will also set PRDET to TRUE)
C         PLDET FALSE

C========= Analysis steering ======

C  Make Event ntuple ? (no-op with the default ZAUSER)
C
C         MEVNT FALSE

C  Make Jet ntuple ? (no-op with the default ZAUSER)
C
C         MJETNT FALSE

C  How to analyse the VD hits ? (no-op with the default ZAUSER)
C
C         VDMET  1

C  Minimum number of jets to accept the event.
C
C         MINJET  0

C  Make primary vertex by adding tracks until the Xi^2 of the vertex
C  gets bad (DOWNUP TRUE) or by by removing tracks until it gets good
C  (DOWNUP = FALSE)
C
C         DOWNUP FALSE



C  Limiting probability for two showers in the calorimeter to be
C  separated.
C  If the separartion of the two showers is such that the
C  probability >= SHOW_SEP_LIM that two independent meassuerments
C  of the SAME shower would give that same observed separartion (or
C  less), the showers are merged. Hence, big SHOW_SEP_LIM -> many
C  showers merged, and v.v. In particular: SHOW_SEP_LIM=0. means
C  no showers are merged, and the cluster-information will essentially
C  be a copy of the calorimeter information in ZATRS.
C  NB. This parameter only takes effect if ZAUSHO is called as in
C  the example ZAUSER!
C
C         SHOW_SEP_LIM 0.9995

C  Lowest distance between shower start-point and track extrapolation
C  to the calorimeter at which the shower will not be attached
C  to the track (in cm).
C  NB. This parameter only takes effect if ZAUSHO is called as in
C  the example ZAUSER!
C
C         MIN_SEP_CLU_TRK 5.0



Mikael Berggren 2003-03-27