DELPHI Collaboration Sa DELPHI 89-15 PROG 130
NY 22 February 1989
DELSIM DELPHI EVENT GENERATION AND DETECTOR SIMULATION
User’s Guide
DELPHI Collaboration
DELSIM Vers 3.2 DELSIM Vers 3.2
USER’s GUIDE
Many people contributed to the code of the DELPHI event generation and detector simulation pro- grams. Their names can be found in the foreword of the manual and in the routine descriptions. Comments on the present description should be addressed to Per Olof Hulth
Foreword:
This is the DELphi SIMulation user manual which describes the generation of events and their simulation in the DELPHI detector [1]. The aim is to provide a package of routines to simulate the response of the complete detector to various kinds of events. A reference manual which contains the detailed description of the subroutines exists [2]. The program is currently. provided as a PAM file which are read by PATCHY([3].
People who want to use these programs can obtain them from:
Mrs. C. Sletten EP Division CERN tel 2062 room 11-—1-006
The following versions of this document have been issued: Date: Changes: 04/09/84 User manual (DELPHI 84—45 PROG— 6) Obsolete ... 28/10/85 User manual (DELPHI 85-93 PROG— 34) Obsolete ... 01/10/87 Draft version of DELSIM 3.00 User’s Guide Obsolete for version 3.1 08/1/88 DELSIM 3.1 user manual (DELPHI 87-96 PROG— 99) Obsolete for version 3.2 22/02/89 DELSIM 3.2 user manual (DELPHI 89— 15 PROG— 130)
The DELPHI simulation package has been developed by many members of the collaboration. A. de Angelis (Padova) T. Baroncelli (Rome Sanita) M. Berggren (Stockholm) D. Bertrand (Brussels) F. Bianchi (Torino) H. Burmeister (CERN) F. Carena (CERN) Ph. Charpentier (Saclay) E. Dahl— Jensen (Copenhagen) P. van Dam (Amsterdam) G. Damgaard (Copenhagen) M. Davite (Genova) M. De Jode (Brussels) B.van Eijk (CERN) N van E1jndhoven (CERN) G. Gopal (Rutherford) A. Grant (CERN) M. Gros (Saclay) J. Guy (Rutherford) P. Hagen (Oslo) Ph. Herquet (Mons) P.O. Hulth (Stockholm) K. Hultqvist (Stockholm) P.S. Iversen (Bergen) R. Messerli (CERN) T. Moa (Stockholm) K. Monig (Wuppertal) L. Pape (CERN) M. Pepe (Genova) V. Perevozchikov (Serpukhov) C. Poiret (Mons) F. Rademakers (NIKHEF) Y. Sacquin (Saclay) R.C. Shellard (CERN) DELSIM Vers 3.2
Ch. de la Vaissi€re (Paris) H. Wahlen (Wuppertal) Ch. Walck (Stockholm)
This guide is organized in the following chapters:
1. General introduction to the program
2. | Information about the different generators and the how to use them
3. Detector simulation
4. Full simulation of detector modules
5. Constants and conventions used
6. Finally there are several appendices with lists of control cards, particle data, ZEBRA banks and examples of files to run the program etc.
This user guide exists on the CERN VXCRNA computer in the disk DISK$DELPHI in the directory [DPA.SIM.WRUP] in a SGML version, under the name USERDS32.SGML. They can be found also in the CERNVM computer, in the disk PUBXX 192 under the name USERDS32 SGML.
—iv¥-— DELSIM Vers 3.2
Main modifications since the release of DELSIM 3.1:
— New single particle generator allowing for up to 10 independent single particles in the same event [see the control cards in Appendix A on page A.1 and an example in appendix E.7 on page E.10].
— Extended particle codes. New beauty and top particles added. New names for old particles (like F* — DS, etc...)[ see Appendix C on page C.1]
— New EURODEC interface with the new EURODEC 2.1 [see section 3.2 on page 3.2].
— BD and BS meson oscillation [see section 3.7 on page 3.7]
— Module parameters [see section 5.5 on page 5.6]
— New internal checking of tracking, using the routine SXSAVE
— §X banks ~ New ZEBRA bank containing all entry points to the different detectors the ST —track has passed through. DELSIM Vers 3.2
CONTENTS
USER’s GUIDE ... 0... eee eee e eee ence ee eeeeeeeeeenaaes ii
Foreword: . 0.0... cc ete ee eee eee eee eee eee nets eee eeeeenees iii
Main modifications since the release of DELSIM 3.1: ...... 0...0.0... cc eee eee eee eee Vv
Chapter 1: DELSIM FOR PEDESTRIANS ...... 00.0.00. cc eee ee ees 1.1
Chapter 2; GENERAL DESCRIPTION OF DELSIM ...... 0.0.00... c eee eee eee 2.1
2.1 Overview 2... ccc ccc ec cee eee eee eee ee ee eee ee ee ee eee eee eaes 2.1 2.2 Pam files available at CERN ...... 0... cece ee ec ce eee eee cece ee eenes 2.1 2.3 Existing manuals ..... 0... ccc ce ee ec ec eee ee eee eee e ee eee eee eeeeas 2.3 2.4 PAM DELSIM .... ce ec ee ee eee ee eee ee eee eee enna 2.3 2.) Control over the execution of DELSIM ...... 0.0.0.0 cee ee ee eens 2.4 2.6 User selection of pilot patches ...... 0... . ce cece ee ec ee ee eee eee eee enee 2.4 2.7 Control Cards 2... ee ee ne eee eee eee eee eee eee eeeeees 2.5 2.8 Debugging facilities 20... cee tee eee ee eee e ee ence ee nes 2.6 2.9 Random number generators: selecting the nth event ...... 0.00. ccc eee eee ees 2.8 2.10 Histograms and plots... 0... ec ee ee cee ee ee ee eee eee eee ees 2.8 2.11 Naming conventions for routines and COMMONS ...... 0000 eee ee eeeee 2.9 2.12 Input/Output 2... cee ee ee te eee eee eee ee eee eee 2.9 2.13 Fast Simulation .... 0.0... 0. ec cc eee eee ete eee eee ee eeees 2.10
Chapter 3: EVENT GENERATION ...... 0..0. 0.0... ccc ee ce eee eee eee eens 3.1
3.1 Available generators ...... be eee ee eee eee tee e eter eee ete ceans 3.1 3.2 Fragmentationmodels 2... ccc eee ee eee et eee ete eee eens 3.2 3.3 Layout of the Event Generation .. 1.0... 0... cece ee eee ee ee eens 3.2 3.3.1 Subroutine SXGEIN: generating primordial interactions ...... 3.3 3.3.2 Subroutine SXGENE: fragmentation of primordial particles ...... 3.4 3.4 How to select events after generation ...... 2... 00. ccc eee ee ee eee ee eens 3.5 3.5 Short lived particles 2.0... ee eee ee eee ee eee eee eee 3.6 3.6 Change particle masses and lifetimes .... 2.0.0.0... cc ccc eee eee eee eee 3.7 3.7 B°-B° Oscilations ...... 0... ccc cc cee cece cece eee ence eee eees 3.7 3.8 How to use your own external generator 2.0.0.0... eee ee ee ee eens 3.8
Chapter 4: DETECTOR SIMULATION ...... 00.0000 eevee ceceeee eeees 4.1
4.1 Basic package for Detector Simulation ...... 0... 0. cee ce ec ee tees 4.1 4.2 Tracking in general 2... ec ce ee ec eee eee ee eee ee teens 4.2 DELSIM Vers 3.2
4.2.1 Subroutine SXDETX: loop over tracks ...... 0... ccc ce ee ee eee 4.2 4.2.1.1 Subroutine SXTRAF: detailed track following ...... 0.00. 4.2 4.2.1.2 Subroutine SXGSEC: generating secondary interactions ...... 4.2 4.2.1.3 Subroutine SXSIMU: calling detector module simulation...... 4.3 4.3 Distance prediction: predict the distance to next boundary ...... 00eee aee 4.4 4.4 Stopping tracking in a detector 2.0... . cc eee ee eee eee ees 4.4
Chapter 5: FULL SIMULATION OF INDIVIDUAL DETECTOR COMPONENTS ...... 5.1
5.1 Detector Simulation ...... 0... ce ee eee eee ee eee eee eee eens 5.1 5.2 Interface with the full simulation ... 0... 0... ccc ec ee eee eee eee eee 5.1 5.3 Module dependent parameters ...... 0. eee ee eee ee ee ee ee ete tees 5.3 5.4 Loading the detector description data base ... 1... . ee ee ee ee ee ns 5.4 5.5 Fast loading of the data base 2... 1. ee ee ee ee eee ee te ee eee eee 5.6
Chapter 6: GENERATION/SIMULATION DATA ... 0.0... eee eee 6.1
6.1 The Particle Description ...... 0. cee eee ee eee ee eee eee een eees 6.1 6.2 The ZEBRA data structure 2.0... . eeeee eee ee eee eee eee 6.2 6.3 Temporary track bank 1.2... . ceeee ee ee eee eee teenies 6.4
Chapter 7; CONSTANTS AND CONVENTIONS ...... 000 cc cece eee eee eee eens 7.1
Tl Units . 0. cc cc ee ee eee eee eee ee ee eee ete ee eee ees 7.1 7.2 DELPHI coordinate system ... 1... ee ce ee ee ee ee eee eee n nea 7.1 7.3 Conventions for particles... 6... ee ee ee ee eee eee eee ees 7.1 7.4 Track/Vertex labels and types 2.1...... ccc ee ee ee eee eeee 7.2 7.5 Naming conventions for DELPHI detector modules ...... ee eee ee eee 7.3 7.6 Definition of material constants .. 0... 0... cee ee eee ee ee eee eens 7.3
Appendix A) SUMMARY OF DELSIM CONTROL CARDS ...... 0-0. ee ee eee, A.l
Appendix B; ZEBRA BANKS FOR GENERATION/SIMULATION ...... --.0055. B.1 B.1 TOP—bank ...... Lecce ence eee e eee e eee teen eect eee eens B.1 B.2 RAW—bank ...... cee ee ee eee te eee Leeeee ee ee eee eee eens B.1 B.3 Partition Master Bank 2.2.0... 0. ccc ee ee et eee eee eee eee eens B.2 B.4 SE—bank 2... ceee ee ee eee eee eee ee eee eee eee eens B.2 B.5 SP—bank .... ccc ee eee eee ee ee eee eee eee ee eee eee B.3 B.6 ST—bank 0... ccc ccc ee ee ee ee ee ee eee eee eee eee ees B.3 B.7 SX—bank .... ccc ee ee eee eee ee eee eee ee eee ee tee eee eee tees B.4 B.8 SI—bank 2... ee ee ee ee eee eee eee ee eee eee eens B.4 B.9 SH—bank .... cece ee ee ee ee eee ee ee ee eee ee eee tees B.5
Appendix C: PARTICLE DATA TABLE ...... 6. cece cece eee ee teen eens C.1 DELSIM Vers 3.2
Appendix D: © DEFINITION OF DECAY CONSTANTS ...... eee eee eee ees D.1
Appendix E: RUN EXAMPLES ... 1... ccc cee eee eee eee eee eee e eens E.1
E.1 Run decks at CERN VXCRNA_ 2... ccc ce ee ee te te eet eee eens E.1 E.2 Create a EXE file on the CERN VXCRNA ... 2c ee ee eee E.2 E.3 Create a histogramming and plotting program in the VM ..... 1... ee eee eee ee eee E.4 E.4 Example on how to use the SXGSEL routine ...... ee eee eee eens E.7 E.5 Control card file 2... ocee ee ee eee ee eee eee e eee E.9 E.6 Example of control cards file for a run with Bhabha scattering ...... --4-- E.10 E.7 Example of control cards file for a run with single 2.1.6...6... eee ee eee ee eee E.10 E.8 Debug listing in the generation phase ... 1... . eee eee ee eee ee eens E.11 E.9 Debug listing of the simulation history, ©... 0.6... eee eee ee eee eee eee eens E.12 E.10 Debug listing of the Zebra structure 2.6... eee eee eee ees E.12
Reference and index tables 2.0... 0. ee ee ee eee eee eee eee eens 1
DELSIM control cards index ...... 0... cee ee ee ee eee ee ee eee ee ete eens 2
DELSIM subroutine index ...... 0.0. cee eee ee ee eee eee eee eee eens 4
General DELSIM index .. 0... 0.0... ee ee eee ee ee eee eee ee eee eee eee 5
TABLES
1. Naming conventions for Detector modules ..... 6.6... ee eee eee eee tee eens 7.4
FIGURES
1. Schematic layout of the event generation ©... 2... eee eee eee eet eens 3.5
2. Schematic layout of the detector simulation ...... 6... e eee eee ee eee eee ee eee ees 4.3
3. Interface with detector simulation .... 0... eee ee eee ee eee teens 5.3 6.2 4. Top Structure of ZEBRA banks ...... cece cece eet teen eet t enn 6.3 5. Data Structure for the Simulation data ZEBRA banks ...... 2... eee ee eee eee eee eee 6.5 6. Data Structure for the Simulation raw data ZEBRA banks ...... -....5 eee ee eee 7.5 7. General view of one quadrant of the DELPHI detector...... ---eee ee ee eres DELSIM Vers 3.2
Chapter 1
DELSIM FOR PEDESTRIANS
The DELPHI collaboration decided in 1982 to develop its own simulation package DELSIM. It is the only LEP group not using the GEANT simulation package. The program was developed start- ing from different (revised) routines that where already existing from the bubble chamber experiments, the Split Field Magnet experiment at CERN ISR, UAI, etc...
The program includes the generation of primordial interactions e*e~ of physical interest and the simulation of the particle interactions with the detector components.
The result of a DELSIM run may be used to test the response of the detector to the physical interactions, to test the software for physical analysis and in real running situation, to compare and serve as reference to the events coming from real life. The structure of the program is designed so as to allow a great deal of flexibility on the control of the running conditions by the user.
The novice at DELSIM can have a start by running the program SIMGO as it stands. If you are running in the VXCERN, copy the command file and the CONTROL CARDS file to your own area. You will find them in DISK$DELPHI:[DPA.SIM]JSIMGO.COM and SIMGO.TIT (for the CONTROL CARDS). In the CERNVM the command file and control cards file are joined in a sin- gle file in the minidisk PUBXX 197 (your G disk) under the name SIMGO EXEC G. The command files are to be runned as BATCH jobs:
SUBMIT/Q=SYSSSHORT SIMGO in the VAX and
BATCH SUBMIT SIMGO
in the VM/CMS). This program will generate (NEVMAX) 5 events of the process IGENER=2 (ete” > Z°(>p*yn~) H(> ££ )), where the Higgs mass (XMH) is 15.0 GeV/c*. The debug option, in the CONTROL CARDS (in SIMGO.TIT), which is set to
C-- Debug options IFEVDB 1 ILEVDB 5 ISWIDB 100 forces the particle information of the generated events from event number (IFEVDB) 1 to (ILEVDB) 5 to be debuged (printed out), once the generator debug (ISWIDB 100) is ON. Actually, you should be carefull, for setting the generator debug option for more than a few events, or even more the simulation debug (ISWIDB 0 1 0 or 0 0 1) for a single event , will generate an enormous output of printed lines (ten’s of thousands).
You could now change the running conditions of your program, by changing some of the CONTROL CARDS. You may, for example, activate the the simulation by changing ISIMUL to 2,
-1l1- DELSIM Vers 3.2
and activating the tracking detectors, ID, TPC, OD, FCA and FCB, by changing the CONTROL CARDs,
G -- Do detailed simulation in the following detectors MSIM 'ID' 'TPC' 'OD' 'FCA' ‘FCB! and output the simulated RAW data for the above given detectors, by setting
C -- Output the raw data at unit ITOUT, in ZEBRA exchange format IDTOUT 3
Try now to reconstruct the events, using this output and the DELANA program.
If you want to make histograms and/or corrections to the program, adding external generators, etc..., you should copy the files SIMRUN.COM and SIMRUN.TIT to your area, do the necessary modifications to satisfy your needs and then plunge into this USER GUIDE.
In the CERNVM G disk you will find DELSIM run examples to write the output either into disk (DELSIMRD EXEC), or into tape (DELSIMRT EXEC), or into cassetes (DELSIMRC EXEC). Modifications into the program and to the CONTROL CARDS for this runs can be made directly into those files when copied into your own area.
There is a DELPHI PRODUCTION OFFICE setup at CERN, to take care of long simulation jobs, to which you have to provide the CONTROL CARDS file for your specific job.
-—12- DELSIM Vers 3.2
Chapter 2
GENERAL DESCRIPTION OF DELSIM
2.1 Overview
The DELSIM basic software includes: l. Physics Simulation. Physics routines generating most of the interesting interactions at LEP. There is a limited choice of generators, as not all processes can be provided in a single pro- gram, but an interface exists which allows new generating routines to be added to the pro- gram, and also one, which may read in, externally generated events. The program uses two different Monte Carlo programs (LUND [4] and EUROJET [5] ) for quark fragmentation and the events are described by the ZEBRA data structure.
2. Detector description. A package of routines which track particles through the detector and produce secondary interactions in the material. The description of the detector is obtained - from the DELPHI detector description data base, via the DDAPP package [6]
3. Detector simulation. An interface to “detector® software which treats the behaviour of parti- cles in the different detector components in detail and produces space points and electronics signals. The “detector dependent” software itself is available on other Pam files, one per detector module (VDSIM, IDSIM,..etc) and 1s described elsewhere [7].
4. Output routines. The output, from the detector dependent software, can be written as raw data simulating the real hardware format, and into TANAGRA banks [8].
The full stimulation of an event in the DELPHI detector is very time consuming, most of the time being spent in the detector simulation modules. On the other hand, the accuracy required from the detector simulation depends strongly on the problem, e.g. raw data simulation requires much more accuracy than is needed to answer some physics questions. Therefore, several levels of accuracy will be provided and currently two such levels are implemented: the full simulation and the fast simulation [9]. The full simulation corresponds to the definition given above. For simulations which do not need the exact details in the secondary processes and detector response, the fast simulation can be used. The fast simulation uses the same generation routines as DELSIM but has special routines for the particle tracking and the detector simulation.
2.2 Pam files available at CERN
There are small jobs with example runs, in the beginning of the DELSIM32 Pam file . These can be very useful to help users to begin. They contain a job creating a library of the simulation rou- tines and a job for the execution of a run for IBM , Apollo, Nord and VAX.
Pam files and correction cradles are kept under standard names on the CERN VXCRNA system. On the VXCRNA under user name DPA (Delphi Programme Area), in the directory
- 2.1- DELSIM Vers 3.2
DISK$DELPHI:[DPA.SIM] there are the following files (normally in card formats) (see Appendix E on page E.1 for full information):
DELSIM32.CAR DELSIM card pam version 3.2
DELSIMLIB.COM deck to produce the library with DELSIM routines SIMDUMLIB.COM deck to produce library with dummy routines SIMMODLIB.COM deck to make the library with the detector modules
SIMCRA32.CAR correction cradle for DELSIM version 3.2 MODCRA32.CAR correction cradle for module pams
SIMGO.COM run deck SIMRUN.COM run deck, with PATCHY changes possible
VDSIM.CAR Micro vertex detector pam IDSIM.CAR ~ Inner detector pam TPCSIM.CAR Track projection chamber pam RICHALL.CAR Ring imaging cherenkov pam (also including Analysis part) ODSIM.CAR Outer detector pam HPCSIM.CAR High density projection chamber pam TOFSIM.CAR Time of flight detector pam MUBSIM.CAR Barrel muon detector pam FCASIM.CAR Forward chamber A pam FCBSIM.CAR Forward chamber B pam SATSIM.CAR Small angle tagger pam MUFSIM.CAR Forward muon detector pam HADSIM.CAR Hadron calorimeter pam EMFSIM.CAR Forward electromagnetic calorimeter pam
All the files with extension CAR can be found in the group disk G of the CERNVM with filetype CARDS. The COM files are EXEC files in the VM, with the following translation of names (the VM files take only 8 letters): SIMRUN —+ DELSIMRD (output on disk) —+ DELSIMRT (output on tape) —+ DELSIMRC (output on cassette) DELSIMLIB — DELSIM32 SIMDUMLIB — DUMSIM32 SIMMODLIB — MODSIM32
In addition to the standard CERN libraries, which include the LUND Monte Carlo, one needs the EUROJET Monte Carlo EURODEC.CAR and EUROLIB.COM (the deck to produce the EUROJET library), which are in the [DPA.SIM] area in the VXCERN and in the G disk in the CERNVM, as well as the TANAGRA library, which is in the [DPA.TANAGRA] (in the G disk in the CERNVM). The libraries available are DELSIM32.0LB, SIMDUM.OLB, MODSIM.OLB and EURODEC.OLB (the extension OLB — TXTLIB in the CERNVM). In addition, there is one data "file used by the HPC module, called PEGSDAT.DAT (extension DAT is DATA on VM).
The most up — to — date information about the simulation can be found in the files:
[DPA.SIM]O_INFORM_DELSIM.TXT in the VAX,and
— 2.2- DELSIM Vers 3.2
DELSIM STATUS G in the CERNVM.
The user is strongly recommended to read these files from time to time!
There is also a development area DISK$DELPHI:[DPADEV.SIM] which includes the latest changes to the program. This area, however, is subject to sudden updates without warnings, and has to be used with caution. It is for developers and not recommended to the general user. The libraries in this area have been compiled in DEBUG/NOOPT/CHECK = ALL mode in order to make bug hunt- ing easier. The equivalent development area in the VM system is the disk PUBXX 400
2.3 Existing manuals
This manual, together with the DELSIM reference manual [2], provides information which should (hopefully!) be sufficient for the use of the existing programs.
The detector dependent code 1s described elsewhere [7].
2.4 PAM DELSIM
This Pam file contains:
— steering and specialised routines containing the high level logic,
—a set of different generators of primordial interactions,
~— service routines which create or access the ZEBRA data structure (e.g. I/O),
— routines depending closely on the detector,
— routines to treat secondary electromagnetic processes,
— hadronic interactions,
— decays,
— particle tracking facilities,
— routines with conventions established for DELPHI, such as the particle definitions,
— utility routines.
— 2.3- DELSIM Vers 3.2
2.5 Control over the execution of DELSIM
The control of the execution of the program can be handled by means of three different mecha- nisms, as follows:
l. PATCHY: + USE statements
The most basic choices are made by the use of different “pilot” patches. A user working on a specific problem does not normally need to change his choice of pilot patch and hence recompile large parts of the program. The selection of pilot patches is described further in section 2.6 However a user may often want to select a few subroutines with + USE statements.
2. CONTROL CARDS (you will probably want to change these)
Most of the running conditions can be changed without recompiling as they are defined by constants. Default values are set at the initialization of the program but they can be overwritten by values spect- fied on an external file.
3. ZEBRA titles (you are unlikely to want to change these)
Some values of constants which the user will not frequently need to change are given in the form of ZEBRA titles. Currently, this contains only particle decay constants (SIMRUND.ASD on the VAX and SIMDEC DATA on VM).
2.6 User selection of pilot patches
The easiest way to start is to take one of the example jobs that can be found at the beginning of the Pam DELSIM and to execute it. The jobs are split in two: first to create a library, second to exe- cute with a minimal amount of code to be compiled (on the CERN VXCRNA and on the CERNVM, all the libraries you need are already prepared).
There are several pilot patches for different computers. The pilot patches are activated by the patchy + USE cards. The initialization of the histogram package HBOOK4 is done by the patchy card +USE, HBOOK4. The activation of the detectors modules is set by inhibiting the + USE,P = DUMMOD cards, that is by setting,p.ex.,
+USE , P=DUMMOD, D=VD , T=1.
will inhibit the DUMMOD patch corresponding to the Vertex Detector and the linker will take the VD module from the MODSIM library.
—- 2.4- DELSIM Vers 3.2
2.7 Control Cards
The steering of the simulation is under your control through the CONTROL CARDS. Although the default values for run constants, defined by the routine SXDATA, are called at the ini- tialization of the program, they can be easily changed (without recompiling the program), through the CONTROL CARDS, which are automatically read at the start of execution (they just overwrite the defaults at the end of routine SXDATA).
At VXCERN the control cards file is named SIMRUN.TIT and in the running program this file is assigned to the unit 15 (default). At CERNVM, the control cards file is joined to the EXEC file which runs the program.
The CONTROL CARDS for the generation of an et*e™ — Z° event, at a beam momentum of 46 GeV/c, and forcing the Z° to decay to c c only, could look like (the C— — cards are just comment — cards):
C--— list control cards LIST C-- Choose beam energy EBEAM 46 C-- Select standard ZO generator IGENER 1 C-- Select CHARM decay mode of ZO C-- nue e ud numu mu c s nutau taut b JPSEL 0 00 0 0 010 0 0 00 C-- Number of generated events NEVMAX 10 C-- Select only the generation of the events ISIMUL 0 C-—- Build SP and ST banks for the decays of the short lived particles JSHORT TRUE C-—- Print debug information about generation from event IFEVDB C-- to event ILEVDB IFEVDB 1 ILEVDB 10 ISWIDB 100 C--Read pre-loaded database LDBZEB TRUE END
The JPSEL controls the decay modes of the Z° and contain 12 elements (for 3 families!), which are put to 1 by default, enabling all decay modes. In the case above, all elements, except element 7 ( c ‘c), are set to 0. The detailed definition of the CONTROL CARDS can be found in appendix A on page A.1.
The CONTROL CARDS are read by the routine SXREAD which uses the FFREAD [10] package. The control card starts with the name of the variable and continues then with the wanted value(s). The position of the values on the card is free and it is possible to continue on a new card if necessary. For vector variables, the elements in the vector can be reached as in
I The CONTROL CARDS inside the program are read by the FFREAD statement
CALL FFKEY ('keyword',variable,variable dimension,variable type)
—- 2.5- DELSIM Vers 3.2
IDB 57=1 which sets the element 57 in the Lund vector IDB to 1, and tells Lund that the Lambda should decay during the fragmentation (default value in DELSIM is 0).
The user can also add his own control cards by using the subroutine SXUFFR (see the reference manual). An example of this is given in Appendix E.3 on page E.4.
A few general points are:
— In the standard mode the program generates the events and simulates the detector in a single pass. But, by setting suitable control cards, it is possible to generate the events and output them as a first step, then read them in again and perform the detector simulation as a second step. The input/output format can be, either the ZEBRA bank structure or the LUND common format LUJETS.
— You can turn on the printing and debugging of events for different levels.
— You can choose the processes for the event generation and which of the final state quarks and leptons will be produced (e.g. ete” — Z° + 1* 17).
— You can select the active secondary processes (e.g. particle decays, hadronic interactions etc.).
— You choose which of the individual detector simulation processors (eg ID, inner detec- tor) are to be activated.
— The title constants for the beam, event generation and the way of following the track can be modified.
The branching ratios of the (weak) particle decays are not set in the routines SXDATA, but defined in ZEBRA titles at the end of the DELSIM Pam file. They are described in sections 7.6 on page 7.3 and in Appendix D on page D.1. (The files written by PATCHY is called SIMRUND.ASD on the VAX and SIMDEC DATA on the VM).
The detailed description of the interface with the detector dependent processors is found in chap- ter 5 on page 5.1.
2.8 Debugging facilities
There are several different levels of printing, which can be useful for debugging purposes. They are turned on with the control cards at the generation, tracking, secondary processes, or at each different detector module. The control cards IFEVDB and ILEVDB defines the first and last event to be debugged. The control card ISWIDB has three arguments (the fourth argument 1s used internally in the detector module simulation and can not be set by that control card);
— ISWIDB(1) controls the debugging of the generation
— ISIWDB(2) controls the debugging of the tracking
— 2.6—- DELSIM Vers 3.2
— ISIWDB(3) controls the debugging of the secondary processes
There are two levels of debugging, full (extensive) debugging with ISWIDB set to 2, medium level with the card set to 1 and no debugging, with the card set to 0. As an example, to have the event 17 with full (extensive) debugging of the generation, medium level for tracking and full debugging of sec- ondary processes, the control cards should look like:?
IFEVDB 17 ILEVDB 17 ISWIDB 2 1 2
An example of listing of particles generated (with ISWIDB 1 0 0) is given in Appendix E.8 on page E.11. |
In addition, independant debug information can be provided with SXSAVE. The control card IFPRFI and IFPRLA, define the first and last events. The control card IFSTAT allows to generate statistics tables on track endings and secondary processes: IFSTAT=0 no statistics prints at all =] only end of run statistics =2 statistics print at the end of every event Futhermore, within the same limits of event numbers, it is possible to get a detailed printout of all the SP/ST information stored for an event. This list gives the information on what happens with all pri- mary tracks saved by SXSAVE [2] in ZEBRA banks during the simulation (see Appendix E.10 on page E.12). They are controled by: IFPREV=0 no printout =] full printout at the end of every event
The debugging of the detector module simulation is done at three levels, with the control cards MDB1, MDB2 and MDB3, eg., to have low level debugging for the ID, medium level debugging of the TPC and the HPC, and full level for the OD, the control cards look like,
MDB1 ‘ID ' MDB2 ‘TPC ' ‘HPC ' MDB3 ‘OD '
Inside the modules, the module routines should check ISWIDB(4), which is equal to 1 if MDB1 has been set for that detector module, or equal to 2 if MDB2 has been used. The value of ISWIDB(4) is filled in, just before the call to each module simulation routines, respectively. Again, the warning issued above about the large output of the debugging mode is applied as well.
The ZEBRA structure hanging from LTOP and the content of the banks, can be printed by using the control card IZEBDB.
IZEBDB 1
For IZEBDB= 1 the DZSURV will print the structure of the bank, while IZEBDB=2 will print the contents of the banks. An example can be found in Appendix E.10 on page E.12.
2 WARNING: The debugging settings need to be used with much care, for they generate an immense amount of printed lines! One event b b with ISWIDB 1 1 0 , will generate 50 000 printed lines!
—- 2.7— DELSIM Vers 3.2
2.9 Random number generators: selecting the nth event
The generation and detector simulation phases of the program use separate random number sequences. The only random generator actually used is RNDM and the other generators, RANF, RNDM2, RN32, RAN3D and FUNRAN have been rewritten using RNDM. In this way it is possible to restart any event with a given SEED. The SEED’s are printed out at the start of every ITEST event for both the generation and simulation. If you want to restart a special event, you should set the data cards ISEEDG and ISEEDS to the wanted numbers, e.g.,
ISEEDG 1699046369 ISEEDS 1226271181
Be careful not to invent the seeds. A seed which is not extracted from the standard sequence cat: produce a succession of “random” numbers with unpredictible distribution. The seed sequences are dif- ferent on different types of computers e.g. a seed taken from a simulation on VAX cannot be used on an IBM or NORD.
We are for the moment investigating a new random number generator with a much longer sequence, using more than one seed.
2.10 Histograms and plots
The facilities for histograming and plotting in DELSIM are for the moment rudimentary. A user — routine USHIST is called after the simulation phase of each event is finished, and exists on the PAM as a dummy routine. HBOOK has to be initialiazed by + USE, HBOOK4, and the histograms created are printed in the output and the HPLOT version of them will be written as a metafile. The printed version of the plots can be obtained by instruction:
GKS3812/PRTR=xxxxx PLOTFILE.MTF
An example of user written USHIST can be seen in appendix E.3 on page E.4. That example uses the ZEBRA history banks SH (see 6.2 on page 6.2), but the Lund common can also be accessed if preferred. The Patchy sequence card +CDE, LUJETS has then to be added. People using the Lund common for analysis can use the function LSTLUN which gives the link LST to the correspon- dant ST bank given the particles line number in the Lund common.
LST = LSTLUN (LINE)
A possiblity to use the standard DELPHI graphic package for displaying events is available which uses the TANAGRA TE and TS banks. If the control card JTETS is set TRUE and the standard dummy module routine library has been loaded instead of the full module library, the program will write out TE and TS banks out on the standard TANAGRA unit. The routines SXTETD and SXTSTK are used for creating the TANAGRA VETBAS structure. This structure can then be used as input for the DELPHI standard graphics program DELGRA [11]. As an example to use this pos- sibility, you should add to your PATCHY cards, in the SIMRUN.COM, the increase of the TANAGRA store and add CONTROL cards (if it is not there ), in the following way:
—- 2.8— DELSIM Vers 3.2
+KEEP ,SXSIZET. PARAMETER (CITSIZE=200000) WHEREAS STEERING DATA FILE 8888S ERASERS JTETS TRUE C-- TANAGRA output at unit LOUTAN (same as standard ZEBRA unit) LABO ‘CERN’ IDTANA 3 LOUTAN 21
You should also remove the linking card for MODSIM in your SSMRUN.COM in order to get only the dummies. This is achieved by setting the option card to EXE mode in the USE of DUMMOD, eg., to get the dummy RICH modules, one set in the running cradle:
+USE , P=DUMMOD,P=RIB,T=E. +USE ,P=DUMMOD,P=RIF,T=E.
2.11 Naming conventions for routines and COMMONs
Names in the Pam files follow the Delphi software conventions as closely as possible. For exam- ple the leading letter of a routine or a common block name is ’S’ for simulation or — in preparation of an utility Pam file — ’U’ for utility. In case of an integer function the ’S’ or ’U’ is preceeded by an ‘I’ (‘IS’ and ‘IU’). A second letter ’“X’ indicates a general facility. A number of routines serving as defaults for the detailed module simulation interface have names starting with ‘Su’, where ’S’ as usual stands for simulation and ’u’ denotes a module of DELPHI. See section 7.5 on page 7.3 and table Table 1 on page 7.4, for details. |
Common block names (and their corresponding sequence name) are initiated “SXC’ with ’C’ for common block. Likewise sequence names of equivalence statements are initiated by “SXE’.
2.12 Input/Output
The different input and output streams are controlled with the control cards. The events are written out at the end of the routine SXLOOP, after the generation and the simulation have been fin- ished. The output will contain generation data and also data from the detector simulation if that has been selected. If one wants to save only the information after the generation, it is possible to write out the event in two forms: in standard ZEBRA format (see section 6.2 on page 6.2), or in the form of the Lund common LUJETS. In the first case the the control card IDTOUT should be used (see appendix A on page A.1 for more details) and the output unit number is given by the card ITOUT (default = 21). The information of the Lund common LUJETS will be written out when the control card IDLUUT is set different from zero. The format of the output record 1s given in the DELSIM ref- erence manual [2] for the routine SXWRLU.
If full simulation has been requested (ISIMUL different from zero) the raw data banks will auto- matically be written out, together with the ZEBRA structure as above. The TANAGRA information will be written out (if IDTANA different from 0) on the same unit as ZEBRA. The unit for TANAGRA is defined by the control card LOUTAN.
Events which have been generated earlier and written out as mentioned above, can be read in again. With the control card IDTIN different from zero (see appendix A on page A.1 for details) the
— 2.9- DELSIM Vers 3.2
ZEBRA structure is read in in a standard form. If the SH banks are included in the structure it is also possible to build up the Lund common LUJETS again (setting the control card JFLGLU = TRUE).
If the information from the Lund common LUJETS has been saved earlier, or an external genera- tor has written a file with the same format, it can be read in by DELSIM, by setting the control card IDLUIN equal to the logical unit number. The data will be read in by the routine SXRDLU (see DELSIM reference manual [2] for the detailed format). The DELSIM ZEBRA structure will auto- matically be built up.
You can select to start on a specific event on the input file, by giving the event number via the control card IEV1. Eg., start on event 55 on the input file:
IEV1 55
In order to keep the information about the conditions in which the events were generated and simulated, a start of run record is written out at the initialization phase (see DELSIM reference manual [2] for more details). Also an end of run record is written out when the program ends.
A “pilot” record including a short summary of the event is written out before the normal ZEBRA structure. See DELSIM reference manual for more details.
2.13 Fast Simulation
The fast simulation uses the standard DELSIM generator routines and CONTROL CARDS, but it does a faster tracking and uses a simplified detector description. To run the fast ver- sion of the simulation it is necessary to set the control card
JFAST TRUE and to link the fast libraries in the way described in the fast simulation writeups [9]. The routines inside DELSIM will then call the fast versions of the routines. The fast routines exists on the VXCRNB at CERN, on [DPA.SIM.FAST].
— 2.10 - DELSIM Vers 3.2
Chapter 3
EVENT GENERATION
3.1 Available generators
Various physical processes can be generated by the generators inside DELSIM. The selection of the process is made by setting the variable IGENER to the wanted value on the control card file. At present the user can choose one of the following processes:
IGENER ete >~y+Z°ff — ete + Z° + HZ, Ho off 22+ qq
WN ete+> H*H-, Hoff
B& ete yy
WM single particle generation (up to 5 particles can be generated simultaneously) 11 ete” + y + Z° > sqsq 13 ete +y + Z° > slp sip 14 ete > y + Z° +f f with radiative corrections 15 ete” + y + Z°->f fusing the LUEEVT routine in LUND 99 User supplied generator (see below)
In the above processes, f f can be a lepton- antilepton or a quark- antiquark pair. The decay modes includes 3 families and the different channels can be chosen by the data cards. The name of the © key 1s different for each generator but the order is the same. The steering of the decays of the Z° for the generators 1 and 14 have the key JPSEL which means:
JPSEL (1) v v (electrons) JPSEL (2) et em JPSEL (3) uu JPSEL (4) dd JPSEL (5) v v (muons) JPSEL (6) ut pn JPSEL (7) ce JPSEL (8) SS. JPSEL (9) v v (tau) JPSEL(10) et JPSEL(11) tt JPSEL(12) bb
The generators producing two particles (like IGENER = 2 which gives Z° and H°) have two different keys one for each particle (JPSELZ for the Z° and JPSELH for the H®). See appendix A on page A.1 or the descriptions of the different generators in the DELSIM reference manual [2], for the exact names. The default values are always 1 which means that all decay channels are possible. Any decay mode can be suppressed (see the run example in section E on page E.1 ) by setting the corre- sponding element to 0.
- 3.1- DELSIM Vers 3.2
In the case of a quark- antiquark pair, hard gluon emission can be included and the subsequent hadronization is treated by the Lund Monte Carlo program.
In the production of (H° + Z°) via a virtual Z°, the matrix element includes both Z° propagators and hence the angular distributions are applicable on the Z° peak as well as above the Z°.
The IGENER = 14 generator is the Berends, Kleiss and Jadach generator [12] with radiative corrections including the Bhabha scattering. This generator is recommended to use instead of using the old DELSIM radiative correction routine. An example of control cards for running Bhabha events is given in appendix E.6 on page E.10.
The standard LUND Monte Carlo (for quarks only) generator LUEEVT is called when using IGENER = 15. The steering of this generator 1s done through the standard LUND variables which are defined as control cards (see appendix A on page A.1).
DELSIM can read an externally generated LUND common (LUJETS) and lift the ZEBRA structure and then continue the simulation inside the DELPHI detector. In this way any generator providing LUND common can be used. If you want to interface your own generator you supply the user routine SXUSGE. This routine will be called for IGENER = 99. See section 3.8 on page 3.8 for more details.
3.2 Fragmentation models
In DELSIM the fragmentation of the quarks can be done either with the LUND Monte Carlo (default) [4] or with the EUROJET [5] Monte Carlo. The LUND Monte Carlo, which is the default in DELSIM, can be steered with the help of the CONTROL CARDS, all the standard choices can be made through them (see appendix A on page A.1). When choosing the LUND fragmentation mode, the shower fragmentation model is the default. If you want to select the ‘old’ string fragmentation model in LUND, set the control card:
MSTE 2
To use the EUROJET Monte Carlo, you must first set the CONTROL card
EUROFR TRUE
The EUROJET parameters can be modified thru the EURODEC TITLE file, which 1s self explana- tory. You will find this file in DISK$DELPHI:[DPA.SIMJEURODEC.TIT in VXCERN and EURODEC TITLE G in the PUBXX 197 DELPHI group disk (CERNVM). More information about the EUROJET can also be found in DELSIM reference manual [2].
3.3 Layout of the Event Generation
The generation of events consists of two parts: the first is executed by the routine SXGEIN, which generates the primordial interaction, leading to leptons or quarks, while the second, executed by SXGENE, does the steering for the fragmentation of the qq pairs (with or without gluons). The interface with the LUND or EUROJET Monte Carlos is done through the LUND common LUJETS. The partons generated by DELSIM are copied over to the LUND common, and after frag- mentation are copied back into the standard DELSIM structure. Below, we describe the main features
— 3.2- DELSIM Vers 3.2
of the event generation. We refer the reader who is interested on the technical details of the actual usage, to the DELSIM reference manual [2].
3.3.1 Subroutine SXGEIN: generating primordial interactions
This steering routine generates the primordial interaction, i.e., the e*e™ interaction down to the state containing final leptons or quarks. The fragmentation of quarks is done later in SXGENE. The steering calls the following routines:
— SXBEAM : to generate the e* e~ beam energy. Options are available to give the beam a Gaussian or rectangular distribution (control card IBEAM, =1 gaussian, =2 constant), with a given spread (DEBEAM). The interaction point can have a gaussian distribution in 3 dimensions, bby using the control card XYZW.
— Primordial process : generates the angular distribution in its own rest frame. These processes are initialised by a call to the routine SXIMAT. The user specifies the value of sin’@,, ( the sine square of the weak angle, control card SSQT) and the routine computes the corresponding coupling constants at initialisation. In the case of IGENER = 14, the generator with radiative corrections, three other constants are used (AMZ, AMTOP, AMHIGS) to calculate the parameters, when the con- trol card IZ1LOP is equal 1. You can choose the leptons or quarks to be generated. According to the menu one of the following generation routines are called:
— — SXZZ: corresponds to the creation of aq q or 1 1 via the exchange of y or Z°, based on the Glashow- Weinberg- Salam model.
— — SXHZ: generates the process et e~ — H° + Z°, where both the H®° and the Z° are allowed to decay according to their decay branching ratios.
— — SXHH: generates the process et e" + H* + H™, followed by the decay of the Higgs parti- cles, whose widths are proportional to the square of the mass of the decay products. Hence, if the Higgs mass is sufficiently large, they will decay dominantly to t+ b and b+t. tae
— — SXEEGG: generates the process e* e~ — y y, according to the standard QED matrix ele- ment. It also allows for form factors or excited electron exchange.
—— SXSQA , SXSQG and SXSLA : generates the processes ete” — y + Z°, followed by their fragmentation to supersymmetric particles.
—— SXSING: generates single particles, within a user defined angular and momentum range. This can be used as an alternative to real physics processes, e.g., to study acceptances. The control cards are given in appendix A on page A.1 and an example in appendix E.7 on page E.10.
—— LKLEIS: Berends, Kleiss and Jadach generator [12] with radiative corrections. See DELSIM reference manual [2] for more detailed information. An example of control cards for this generator is given in appendix E.6 on page E.10.
—— SXLUND.: calling the standard LUND Monte Carlo generator LUEEVT [4]. In this case the SXBEAM is NOT called, but the beam energy is transfered from the control card. The ZEBRA structure is lifted inside this routine.
—- 3.3- DELSIM Vers 3.2
—— SXUINT: interface routine for user supplied external generator. The routine is calling the user supplied routine SXUSGE which should return the generated particles in the LUND common LUJETS. The ZEBRA structure 1s lifted inside SXUINT.
3.3.2 Subroutine SXGENE: fragmentation of primordial particles
This is the steering routine which completes the fragmentation to the “stable” final state particles (not used in the case of IGENER = 15 or 99!). Gluons can be generated and the fragmentation of quarks and gluons takes place. The communication with the LUND fragmentation is done via the LUND common. SXGENE calls the following subroutines (see Figure 1 on page 3.5):
— SXGLUN : routine that generates gluons, makes all partons fragment and handles the decay of resonances, 7°’s etc , by calling the LUND Monte Carlo, latest version.
— SXEJET is used to interface DELSIM with the EUROJET fragmentation scheme.
SXGSUS is called through SXGLUN to handle the supersymmetrical cases.
SXLULDP : fills the LUND common if the primordial interaction leads to leptons.
SXLULB : rotates the particles according to the jet production angles and transforms all parti- cles from their production frame to the lab system in the Lund common LUJETS.
~— SXLUZE : If requested (JFLGSH = TRUE) the ZEBRA fragmentation history banks SH are lifted, together with the vertex and track banks SP and ST (see section 6.2 on page 6.2 for more details). The secondary vertices from the selected short lived particles ( like t- leptons, etc) are also lifted, if requested (ISHORT = TRUE).
— SXLUST : If no SH structure is requested, only the SP/ST banks will be lifted.
The event (as it occurred, inside the beam pipe) is now complete and can be used for histogram- ming, used by the detector simulation or be written out on disk (tape). However, for many applica- . tions the event generation is very fast. Thus, it is often convenient to regenerate the same events for several different conditions in the detectors.
— 3.4—- DELSIM Vers 3.2
OXGENE :
Oo
Quarks \ Leptons \
SNLULP ¥ TUTTE Lepton decay UTE
Canvertta - Jab system-
if na SH \ é if SH. \f
December 1987 Figure 1: Schematic layout of the event generation
3.4 How to select events after generation
It might be the case that you wants to select events with a certain topology, a certain particle composition, a certain energy-flow pattern, etc. To facilitate such selections,.a routine SXGSEL is called after the generation step. This routine already includes the LUND common blocks and the ZEBRA banks, as well as code needed to tidy up if the event is rejected. Thus, you need not bother about this. The actual code of the selection criteria should be supplied, as a KEEP sequence with the name SXGSELBODY in your cradle, where the variable IUSEIT should be set to zero if the event is rejected. The control card NGMAX (default = 1) controls how many tries are allowed in each event. If this limit is surpassed, the programs stops.
In the Appendix E.4 on page E.7 one finds two examples of how to use this facility.
At the end of a run, the number of generated events will be printed out, as well as the fraction of these that passed the selection-criteria. As a word of caution, it should be pointed out that the distri- —- 3.5- DELSIM Vers 3.2
bution of accepted events is a negative binomial (“Keep on trying until You get a predefined number of accepted events”), rather than binomial (“Generate a fixed number of events and then check how many were accepted”). This implies that for a small sample, the error on the branching ratio is not
1/¥ number of accepted events but rather something bigger (and more asymmetric).
3.5 Short lived particles
The short lived particles like tau leptons, charmed and beauty particles will never reach the beam pipe and they can be forced to decay inside the generation phase of the program. The list of particles (the number in DELPHI code) which should decay are defined inside the vector JSDECY. The length of the vector is NSDECY and is for the moment 31 (twenty one are not used). The default particles are:
TAU, D®°, D*, Ft, A,, CSU00+, CSD00, BU, BD and BS.
The particles decay using the LUND Monte Carlo or EUROJET, except for the directly pro- duced t’s from Z° (IGENER .= 1 and 14), which uses the DELSIM routines, in order to keep the information about the polarization.
If you want to lift the secondary vertices (SP and ST banks, see section 6.2 on page 6.2) of the decay particles, the data card JSHORT should be set to TRUE. The default value of JSHORT is FALSE which means that the particles will decay and the longlived decay products will belong to the primary vertex. It is necessary to lift the SH banks (which is the default case, JFLGSH is set to TRUE) in order to have the secondary vertices for the short decays. The lifetimes are defined in the routine UPNAM and can be seen in the particle data table in appendix C on page C.1. The decay branching ratios are coming from the LUND Monte Carlo except for the special tau case when the DELSIM decay table is used (see appendix D on page D.1).
The low mass Higgs is a special case since it has (very) mass dependent lifetime. For a higgs mass below twice the mass of the muon, it decays into ete~ and yy. In DELSIM only the H® > e*e7 mode is coded, and the lifetime, for this range of higgs masses, is automatically calculated in the rou- tine SXHITA. The control cards for the higgs case can be as an example on how to modify the list for short decay particles.
C-—- Put the higgs mass XMH 0.20 C-- Increase the number of short decay particles to include Higgs NSDECY 11 JSDECY 11=37 C
3.6 Change particle masses and lifetimes
The particle lifetimes are kept inside a blockdata SXPBLK and is read by the routine UPNAM. It is possible to change the lifetimes by using the control card VTAU. E.g., if you want to change the lifetimes for the beauty particles BU and BS (see appendix A on page A.1) to 1.2 * 10713 you should have the control card
VTAU 125=1.2E-13 127=1.2E-13
— 3.6- DELSIM Vers 3.2
where 125 and 127 are the DELSIM particle numbers (see appendix A on page A.1).
The lifetime of a Standard Neutral Higgs, if its mass (XMH) is less than 2m,, is automatically tak- en into account in the IGENER =2.
To change the particle (quark) masses is possible, via the control card VMAS. However, for the low mass quarks, it is only possible to modify the masses, when using EURODEC (the LUND frag- mentation does not allow it). The top mass can be modified in both fragmentations, by setting either AMTOP or VMAS. To change the TOP quark mass to 42 GeV, set the control card:
AMTOP 42.
The value of the TOP quark mass is transferred to the LUND or EURODEC Monte Carlo and also used when calculating the GSW parameters with radiative corrections (IGENER = 14).
3.7 B® - B® Oscilations
The simulation of the B° B® oscillations have been implemented in DELSIM.
OSCILLATION PARAMETERS. In principle, the formalism of the Be B and B° oscilla- tions is the same than the one governing the K°-K° system. The regime, is quite different however. The oscillation rate depends on two parameters x and y:
Am y= oe yo’ 2y
where Am and Ay. are the mass and decay rates differences between the eigenstates (B° + B°)/./2 and — (B° — B°)/,/2 , and y is the average decay rate. Ay is expected to be small with respect to y (in con--.- trast to the case of K,). Therefore, y can be assumed to be zero and the dependence on y neglected. For the Bi, the parameter x 1 has been recently measured by Argus to be 0.72, and this is taken as the default value. For the still unknown B?, a value for x, can only be guessed. The default value of 18, reflects that the transition B? <> B is expect to be much more stranger than for the BY in the standard model.
TIME DEPENDENCE. The probability to observe an oscillation, when a B° (B°) decays, is a function of the proper time, an exponential multiplied by a sine function. For the Bt, the lifetime and the oscillation period are similar, and a time dependence can be observed. For the B*, the oscillation period is much shorter. A mode has been introduced which allows the user to simulate, this time dependence. If the time dependence is ignored, the likelihood of observing an oscillation, after inte- gration over time, is related to the ratio r = x/(2 + x’), therefore, only x is required.
TITLE CARDS. A few title cards turn on the simulation of oscillations: - BDOS TRUE: activates the B°d oscillations (default FALSE) - BSOS TRUE: activates the B°s oscillations (default FALSE) - XD value: set the value of the xd parameter (default 0.72) - XS value: set the value of the xs parameter (default 18.0) - MODOSC 0 or 1: define the anode of oscillations generation (default 1)
—- 3.7- DELSIM Vers 3.2
(0 = without time dependence, 1 = with time dependence) The decay rates y, and y, can be changed by modifying the lifetimes of the B) and the B’ (title card VTAU).
TECHNIQUE. ‘The simulation requires the LUND framework. When the common LUJETS is created or read from an external generator, it is scanned for BY or B?(B° or B°). If a neutral B is found, a proper time is generated. A likelihood to observe an oscillation is calculated from this proper time, according to MODOSC. If the decision to oscillate is taken, the descendants of the B are scanned in LUJETS, and switched to their antiparticles. The proper time, saved, is used to calculate the range and position of the B decay.
RECOMMENDATIONS. Check that the secondary vertices are lifted (SHORT TRUB), that the list of short lived particles includes the BY and the BY. |
3.8 How to use your own external generator
You may use different generators than the ones provided by the standard DELSIM package. The interface with DELSIM is the standard LUND common LUJETS. You can either generate the LUND common externally on a file, and then read it in by setting the data card IDLUIN equal to the - unit number (DELSIM will call the routine SXRDLU) , or generate the LUND common internally, - inside the user routine SXUSGE. In the later case IGENER should be set to 99. DELSIM will lift the ZEBRA structure in both cases.
When reading an external Lund common file, IGENER should be put to 0. The exact format of the Lund file to read, can be found in DELSIM reference manual [2] in the descriptions of the rou- tines SXKRDLU and SXWRLU. E.g., if you want to read a file with Lund common from unit 12, the cards should look like;
IGENER 0 IDLUIN 12
If you have your own generator and want to interface it with DELSIM, you should supply a routine called SCKUSGE. This user subroutine (which exists as a dummy routine in the DELSIM PAM) is called inside the routine SXUINT which is selected when IGENER is 99.- Your routine should build up the standard Lund common LUJETS with the fragmented particles ( Attention: Parti- cle code = LUND ! ). DELSIM will then lift the ZEBRA structure and continue in the standar way. |
When IGENER = 99 is chosen, a user initialization routine, SXUINI, is called at the begining of the run, and another, SXUEND, at the end of the run. In addition the user has one routine, SXUFFR, which can be used to define user control cards which will be read in the standard way (the routine needs only the call to the FFREAD routine FFKEY since the initialization is done in SXREAD). These routines are dummy routines on the DELSIM PAM. The only routine which it is necessary to supply is SXUSGE.
—- 3.8- DELSIM Vers 3.2
Chapter 4
DETECTOR SIMULATION
4.1 Basic package for Detector Simulation
A package of routines has been written by members of the collaboration for the tracking of parti- cles through the detector. In its minimal version it includes a track following routine with energy loss and multiple scattering only (the data card ISIMUL = 1). The following secondary processes can also be switched on (on = 1 default, off = 0), if the data card ISIMUL = 2.
Process Data card — Delta rays JDRAYS — Bremsstrahlung JBREMS — Pair production JPAIRS — Compton scattering JCOMPT — Decays JDECAY — Nuclear interactions JHAINT — Positron annthilition JANNIH — Photoelectric effect JPHOTO
The hadronic interaction routines are derived from Alan Grant’s Cascade program. The electro- magnetic routines follow what has been done in TATINA, GEAN3 and EGS (see the comments for the different subroutines and reference [13]). Currently, an interface to GHEISHA is under prepara- tion.
The geometry of DELPHI for the track following is expected to be:
(a) from the Detector Description Application package (DDAPP) [6] which extracts geometry information describing the DELPHI detector from the structured data base. The data base can give different levels of details.
(b) in the case of the fast simulation, a much simplified version exists, which can only be used when running the fast version (see ref [9] ).
The interface with the full simulation inside individual detector modules is described in chapter 5 on page 5.1. |
- 4.1 - DELSIM Vers 3.2
4.2 Tracking in general
The basic tracking package is made up of routines that:
a. follow tracks with energy loss and multiple scattering through a variable magnetic field.
b. generate secondary processes — electromagnetic or nuclear interactions or decays — during the tracking.
More complete information about the tracking can be found in reference [2].
4.2.1 Subroutine SXDETX: loop over tracks
This is the steering routine containing the loop over all tracks (from primary and secondary ver- tices) in the ST banks and/or in the temporary stack (see section 6.3 on page 6.4). The routine calls SXTRAF to follow each track. Then it may generate a secondary process (SXGSEC) or call the full tracking through a detector (SKSIMU) (see Figure 2 on page 4.3).
4.2.1.1 Subroutine SXTRAF: detailed track following
SATRAF follows a track in a magnetic field, taking energy loss and multiple scattering into account. — If this option is chosen, it calls the secondary process initialization routines to calculate the length to the interaction point. It works for any kind of detector and field. The interface routine with the detec- tor geometry is SXDDAP, and for the magnetic field SXFELT. The track following can be stopped by giving a maximum track length, a maximum number of spirals allowed or the detector parts at which control is to be returned to SXDETX (see SXSIMU). If the secondary processes are switched on, SXTRAF calls (at every change of material) the subroutine SXPSEC to generate a random track length at which a secondary interaction could occur. If this length is reached within the same material, the control is returned to SXDETX which then calls SXGSEC (see reference [2] for more details). SXTRAF returns as soon as a track enters in a new detector module. It can also return at every new . layer encountered, if the detector is declared as MSTP.
It is possible to mark tracks, in general neutrals, which will force SXTRAF not to stop at every internal boundary. The user can set ISTOPF of the common SXCTRK to nonzero, so that the STOP flag from SXCHKM will be overruled, and SXTRAF will transport the particle right through the users module.
The tracking parameters, STEP, STEPM, etc, in the common SXCTRK can be modified when the control of the tracking is taken by a detector module. When the track leaves the module the parameters are reset to the default values (see the control cards in appendix A on page A.1). In such a way, the tracking can be optimized for the specific detector module.
4.2.1.2 Subroutine SXGSEC: generating secondary interactions
SXGSEC generates the vertex and tracks of a secondary interaction. When such a process occurs, the current track following is normally stopped and SXDETX starts following the next track.
— 42- DELSIM Vers 3.2
OXDETX : DETECTOR SIMULATION
Tirst empty the stack then loop over the ST
f which vmer'errtrack? |
SNGSEC ¥ SX ) Mu SuSiM = Detailed “secondary | =: detector | * tracks £25 simulation __
¥ >
To next track
December 1997 Figure 2: Schematic layout of the detector simulation
4.2.1.3 Subroutine SXSIMU: calling detector module simulation
SXSIMU : if the track reaches a part of the detector where it is supposed to stop, or call for detailed module simulation, control is given to the routine SXSIMU. This routine calls the detailed simulation corresponding to the given detector component. This can perform a more detailed simulation of the track and transmit the track to SXSAVE (e.g., from the exit of the detector).
— 43-
DELSIM Vers 3.2
4.3 Distance prediction: predict the distance to next boundary
When stepping along a track it is possible to get the extrapolated distance to the next change in detector medium, from the DDAPP package [6]. Longer, or more precise track length, can then be followed before having to check for a change in material. All detector modules can select inside their code both ways of stepping. Using the parameters FRACLE, STEPMD, DPREC and IDIST of the common /SXCTRK/ it is possible to change the settings inside a module. The default values can be changed via the data cards with the same names. Inside a detector, the user can again change the parameters, which will be reset to the default values when the tracking leaves the module.
FRACL(E) = fraction of potential length taken for the first step in SXTRAF set higher for neutrals and when tracking in light media, as vacuum or air
STEPMD = maximum step acceptable from distance calculation
DPREC = precision (%) in distance calculation
IDST = ON/OFF flag for use of distance prediction IDST = 1 for distance prediction IDST = 0 for no distance prediction
4.4 Stopping tracking in a detector
It is possible to stop tracking when the track reaches certain detector modules. This is controlled via the control card MSTP. In order to stop the tracking in the detector modules HPC, EMF , COI, SCQ and HAB the card looks like: | MSTP ‘HPC ' ‘EMF ' 'HAB ' 'COI ' 'scq ''
Then, either the next track is processed, or the control is returned to SXSIMU. This enables also a return to SXTRAF for every layer which is encountered.
— 44- DELSIM Vers 3.2
Chapter 5
FULL SIMULATION OF INDIVIDUAL DETECTOR COMPONENTS
5.1 Detector Simulation
The code for the different detector modules have been prepared by the each detector group. The writeups for the modules can be found in ref. [7] and describe the way the processors are working.
Each processor is made up of two distinct parts: l. To determine space points or showers for display purposes and for checking track finding algorithms.
2. To convert these space points into the final electronic channel pulse heights using the appro- priate response functions and adding in realistic noise and background signals.
5.2 Interface with the full simulation
The interface between the basic simulation and the full detector module simulation uses the name conventions summarized in Table 1 on page 7.4.
The interfacing with the basic simulation package is done in the following way:
The data card used for activating modules is MSIM for the full simulation. So, in order to call the TPC and ID modules for full simulation, the data card looks like:
MSIM ‘TPC ' ‘ID !
When a module is selected by MSIM cards, the following routines are called during execution:
— SxINI at the initialisation of the program
— SxBEG at the start of a new event
— SxSIM for the full simulation in the ’x’ module, called for every track entering a component of ’x’ |
— SxEND at the end of the event, when all tracks have been followed
— SxSUM at the end of the run where “x” stands for the short name of the detector component (See Table 1 on page 7.4, Figure 3 on page 5.3).
-— 3.1- DELSIM Vers 3.2
Dummies of the routines have been provided on DELSIM in the Patch DUMMOD. For the full simulation, only the routine SxSIM is compulsory, the other are optional.
If a module is not selected by the control card MSIM, the tracking will go through that module in a normal way, producing interactions depending on the material.
The different module routines are compiled and stored in a library (DELSIMMOD on the VAX). Since one does not necessary want to load all available detector modules (because the EXE file becomes too large on the VAX), it is possible to load dummy routines instead. The dummy routines will automatically be loaded, but can be ignored by PATCHY cards. In that way, the real routines will come from the library. For loading the Barrel Rich, Barrel muon and HPC from the DELSIMMOD library, you should have the cards:
+USE, P=DUMMOD, D= TPC, T=INHIBIT. +USE, P=DUMMOD, D= ID, T=INHIBIT. +USE, P=DUMMOD, D= RIB, T=INHIBIT. +USE, P=DUMMOD, D= MUB, T=INHIBIT. +USE, P=DUMMOD, D= HPC, T=INHIBIT.
These cards will let Patchy skip the dummy modules from the PAM and the loader will take the real routines from the module library.
All modules which are selected with the MSIM control card, will write out the raw data onto the output file. In addition to the standard raw data, the modules can also save the incoming track PA vector, in order to later compare “truth” with DELANA output. To select this option you should select the control card MTRS, with the wanted detector name, eg.,
C-- Save entering tracks in the following detectors MTRS ‘ID ' 'Tpc ' 'op ' 'FCA ' 'FCB ' 'mMUB ' 'MUF '
The detectors are requested to store the first 15 words as standard PA structures, but can choose to add extra module dependent information.
Examples of loading and running DELSIM are described in appendix E on page E.1.
— 3.2- DELSIM Vers 3.2
INTERFACEWITH DETECTOR SIMULATION
SXDATA cimtalse © handles the control cards
SXICON ¥ SUIN
“Initialise—
‘Initialise “detector | ‘detectorus
™ “constants— LYMM:
SXLOOPy
Next
SEWENT ©
TT | next vx SBESEEESSS gf: Next ThE: SPipiiininininietih: : Follow °:: SYSIME
SuSIM
Call Full 2 O*) Individual ooSimulation 3: ‘detector
6
=: routines simulation viene 2 RRO LUC
(*) : calledif the given detector is selectedbu control cards
Figure 3: Interface with detector simulation
5.3 Module dependent parameters
There is a possibility for the different modules to change parameters using the control cards. However, this is only for experts and should not be used by the normal simulation user. Two kinds of parame- ters cards exists:
MOPxxx for general parameters
TRGxxx for trigger parameters
- 3.3-
DELSIM Vers 3.2
where Xxx is the module name, eg., MODTPC, etc. Eg., changes of some default values for TPC looks like, MODTPC 5.0 3.149 TRGTPC 0.0 1989.
The details of how to introduce the parameters and how the module access the information are given in the reference manual [2].
5.4 Loading the detector description data base
The detector description is loaded for you by calls to Detector Description Application Package (DDAPP) [6] routines, from SXDDAP.
— DFMODR defines the (default) run number. For each run number, the valid list of detector names is given in the database. At present, IRUN should normally be set to —2, which is the default value.3
— DEFGEO (DEFCAL) loads the geometrical description ( calibration file ) of a single named detector that corresponds to a specified date and time (in general the description will be time dependent) and to a specified level of details.
DEFGEO and DEFEND only try to load the detectors from the list from DFMODR and the list of available modules provided by DFMODB.
The parameters for these routines are input to the DELSIM program via three control cards DDML, DDDAT and NLEV.
— DDML has 5 arguments which specifies the detector module, the date (DATIME(1)), the time (DATIME(2)), the level of detail for the geometrical description (LEVGM) and the cali- © bration files (LEVS) for each detector individually.
— DDDAT can change the default values of DATIME(1) and DATIME(2), which are given in the SXDATA routine. DDDAT gives the date and time for all the modules ‘which are not specifically defined by the control card DDML above. The default values given (890101. 120000.) will tell DDAPP to load the versions up to Ist of January 1989.
— NLEV can change the default values of LEVG and LEVS for each detector (or other DELPHI constituents) for which these are not specified via DDML.
DATIME(1,2) may be set to some future date, in order to always pick up the latest descriptions of everything.* A date < 1986 should never be used (except with IRUN = —1).
NLEV(1) may be set to: 0 — load no geometrical data
3 The default value is —2 and can be changed by the control card IRUN (see appendix A on page A.1). The run number , IRUN= —1, corresponds to the ‘old’ medium 2 description and is of interest only to professional archeologists (who must specify a 1986 date).
4 Descriptions are given the current date and time when first received and loaded into the data base. They remain valid until _ they are superseded by newer descriptions. At present, once they have been superseded, they are usually dropped entirely, since the change is usually due to an error correction.
—- 54- DELSIM Vers 3.2
] — load average description 2 — load full geometrical data —n — negative means load to the nth. level
NLEV(2) = 1 loads the full calibration files.
To summarize: the control cards used for steering the loading of the data base are
NLEV LEVG LEVS DDDAT DATIME(1) DATIME(2)
for the default values and:
t t DDML module name DATIME(1) DATIME (2) LGEOM LSDEV
for individual selection of module levels.
By using the following values:
DDML "BEA — 890400. 120000. 2. "VD ad 890401. 120000. 1002. "ID -@ 890401. 120000. 1002.
EHO ‘TPC 890401. 120000. 1002. "RIB —- —: 890401. 120000.
ee "OD — 890401. 120000. 1002. "HPC — 890401. 120000. "COI ~—: 890401. 120000.
‘TOF -- 890401. 120000. "HAB ~- 890401. 120000. 1002.
OOOOH
'MUB —
890401. 120000. rE
"FCA ~~? 890401. 120000. 1002. EP ‘RIF — 890401. 120000. "FCB ~~ 890401. 120000. 1002.
FHP "EMF ~~ 890401. 120000. 1002. "HAF - 890401. 120000. 1002. 'MUF -. 890910. 120000. 1002.
FOF "SAT — 890401. 120000.
"HOF —_ 890401. 120000.
OF the proper version on the data base will be loaded. Since the material is very unequally distributed in the BEA and VD, they are recommended to be allways loaded at level 2.
If none of these control cards are given, DELSIM will load all modules with the latest descrip- tion.
Obsolent (Dec ‘’88) sensing device files may be loaded by using DDAPP300 and LEVG=LEVG+ 1000. DEFEND initiates checks on the data. When the geometrical description is loaded from the data base, it will make the binary search tree to speed later access with a given X,Y,Z. Each geometrical data base supplier and user should check his data for consistency, by setting IDDOVE equal to 1. Since this is a fairly slow task, it is not the default.
- 3.5- DELSIM Vers 3.2
5.5 Fast loading of the data base
The loading of the detailed detector description data base, and making checks on it, takes quite a long time, but in order to save time, it is possible to store away the loaded ZEBRA description onto an external file (unit given by the control card LUNDBZ, default value is 59), by setting the data card WDBZEB TRUE. The next time you want to use that same detector description you can set the data card LDBZEB to TRUE, and the pre loaded version will be read in very fast. You save a factor of 20 in loading time! In this last case the DDML, DDAT and NLEV are not used. E.g:
WDBZEB TRUE LDBZEB FALSE the first time you run a specific detector layout and
WDBZEB FALSE LDBZEB TRUE the next time. If the program does not find the ZEBRA database file a call to the fatal ZEBRA rou- tine ZFATAM is done with the message:
" DATA BASE FILE NOT POSSIBLE TO OPEN "
— 3.6 - DELSIM Vers 3.2
Chapter 6
GENERATION/SIMULATION DATA
6.1 The Particle Description
The basic routines communicate through arguments, most of which have a standard definition. The particles are described throughout all the basic routines of the generation and simulation by the same array, called the Particle — Array (PA), which contains the following quantities for each particle:
PA( 1) particle mass code PA( 2) particle mass value PA( 3) Px . PA( 4) Py PA( 5) Pz PA( 6) E PA( 7) P PA( 8) charge PA( 9) x )_ of the point at which PA(10) y ) the momentum vector PA(11) z ) is defined PA(12) track length PA(13) flight time in ns PA(14) track label? PA(15) track type®
The mass code is an integer number (stored in real representation), identifying uniquely the parti- cle mass, and following the convention of subroutine UPNAM(UPCON) (section 7.3 on page 7.1). The conventions for defining the particle label and type are given in section 7.4 on page 7.2. The redundacy in the PA vector (mass, momentum, energy) has been introduced in order to avoid prob- lems with negative square roots due to rounding errors. In addition to the PA array, further informa- tion may be required for some of the routines. These data are described with the corresponding rou- tines.
> When the temporary track bank stack used (see next section), the track label of PA(14) will contain primary track number + 10000 * number of the track branch
6 The track type is the vertex type number of the process that produced this secondary particle.
- 6.1- DELSIM Vers 3.2
6.2 The ZEBRA data structure
The most relevant quantities are stored in the data structure, which is displayed in Figure 4, Fig- ure 5 on page 6.3 and Figure 6 on page 6.5. The detailed description of the contents of the structure banks is to be found in appendix B on page B.1.
TOP
RAW data SE Trigger PA vectors
Figure 4: Top Structure of ZEBRA banks
If we follow the flow of the program, the first bank created is TOP, for the event data. The TOP bank contains a structural list of links supporting the various kinds of header banks for the event | data. In the case of simulation the — 1, —5,-6 and —7 links are used. Hanging from the —5 link is the simulation header bank SE, which contains the quantities defining the incoming e* and e~.
The link —6 supports the extra trigger information. The modules can also write the incoming tracks, in the form of PA vectors, if the MTRS control card has been selected (see 5.2 on page 5.1), which are hanging from LTOP — 7.
Under SE, we have the banks SI which describe the particles coming from the primordial interaction diagrams (see definition in the section on SXGEIN): in the simple case of (y + Z°) exchange, these are the lepton- leptonbar or the q- qbar pairs. For the more complex cases, the SI structure is extended in depth. As an example, we can mention the production of charged Higgs: the first SI bank describes the H+ H~ system and supports 2 down banks which describe the decay of the 2 Higgses to! Torqq. Essentially, the SI bank contains the decay angles in the 2- particle rest frame, as well as the parameters of the Lorentz transformation to the system corresponding to the upper SI bank (if any). The information in the SI banks are used for the Lorentz transformation from the CMS to the laboratory sytem, which is done in the routine SXLULB.
The history of the fragmentation is saved in the SH banks. For each particle an SH bank is lifted, with links pointing to the mother, sister and daughter particles SH banks. The bank contains the 4- momenta in the laboratory system and some LUND information. The Z°, H°, H+, H™, etc., are also stored in these banks. These banks are recommendedto the user who wants to make some analysis. ~The SH banks are lifted if the data card JFLGSH is (default value). TRUE.
—- 6.2- DELSIM Vers 3.2
TOP
5
Simulation header (SE)
1 3 4 5
) ST 4 SH sister
3 SH mother 2 SH daughter
1
SP prim SP sec SI SH.
L
SH SH
5 SI parent 5 , SI parent 4 SP end 4 SP end 3 SP start 3 SP start 2 2
ST prim ST sec
1 1
SX prim | SX sec
Figure 5: Data Structure for the Simulation data ZEBRA banks
The last step in the event generation is the creation of the primary vertex SP, and of all final state particles belonging to it. The latter are described by ST banks, which contain mainly the 4— momenta expressed in the laboratory system. It should be stressed that the meaning of "final state” particles is ambiguous. For example, a K° short may'‘or may not be allowed to decay at the level of the event generation (depending of the setting of the Lund vector IDB, see section E on page E.1). Corre-
— §63 -
DELSIM Vers 3.2
spondingly, it will appear as a final state particle or be replaced by its decay products.
Short lived particles like tau- leptons, charmed and beauty particles, which have lifetimes so short that they never reach the beam pipe, are forced to decay during the generation phase of the program. The SP banks for these secondary vertices can also be lifted inside the generation, which will be done if the data card JSHORT is TRUE (see section 3.5 on page 3.6). The SP banks corresponding to oth- er secondary vertices are not made at the level of the event generation, but are created during the detec- tor simulation, when the track may undergoe an electromagnetic interaction (pair conversion, bremsstrahlung, delta production, Compton, etc.), a nuclear interaction or a decay. The connection between the primary track and the end vertex is expressed through reference links.
The secondary vertices (SP) banks have in addition to the outgoing tracks, also the incoming particle in a ST bank. For the incoming particle, the sign of the momentum is changed and the track length is negative. The single particle generator ( IGENER = 5) has no tracks linked to the primary SP, only to secondary SP’s.
The simulated “raw data” from the detailed module simulation, is hanging from the top bank —1 link. The RAW header bank (Event master bank) contains a structural list of links, supporting the header bank (Partition master bank) of the individual detector modules, RTPC, RHPC, etc... The link number, for a given detector, is defined in the block data MODBLO (see reference [2] ).
The event data layout is also described in reference [14]. A DZSURV of the written ZEBRA structure can be printed out setting the control card IZEBDB= 1 (See Appendix E.10 on page E.12).
6.3. Temporary track bank
Some applications do not need all details of an event throughout the detector. To save time and workspace, an option to make use of a temporary track bank stack is available.
The decision to use ZEBRA banks or the temporary track bank for storing the the track is taken in the routine SXSAVE and depends on the track energy, the type of interaction,etc.. (see the descrip- tion of the routine SXSAVE in the DELSIM Reference Manual [2]).
— 64- DELSIM Vers 3.2
TOP
Event Master Bank (RAW)
n | 1
Global Errors
Partition Master Blank (Rxxx)
5 4 3 2 1
Error W-C
Error | Type
T1/T2 Data source
T3
T4 W-C
Blocket Data
Figure 6: Data Structure for the Simulation raw data ZEBRA banks
—- 6.5 -
DELSIM Vers 3.2
Chapter 7
CONSTANTS AND CONVENTIONS
A set of conventions has been established for the event generation and detector simulation. They are supposed to be followed throughout the whole DELPHI software.
7.1 Units
Throughout all routines of DELSIM the following units are used systematically: distance cm time | sec energy GeV momentum GeV/c mass GeV/c?
7.2 DELPHI coordinate system
This follows the definition in [15]: the global reference frame of the experiment is right handed. The z- axis is pointing in the same direction as:‘the e~ beam, which rotate anticlockwise (as seen from above), while the x axis points towards the centre of LEP. The momentum vectors are defined as: px = p * sin(@) * cos(¢) 0<@<2n py = p * sin(@) * sin(¢) 0 Note the use of polar angle, not dip (the dip should NOT be used). 7.3 Conventions for particles The conventions for particles are kept in the subroutine UPNAM ( Entry point UPCON) and the users are strongly advised to follow this convention throughout the software. The routine UPNAM (UPCON) makes any kind of meaningful conversion between two of the following quanti- ties (COMMON /UCPCON)) : code name /COMMON/ PNAM UPNAME: particle name, a 4— character variable PCOD UPCOD : particle code, an integer identifier PMAS UPMAS : particle mass, the actual mass value PLUN UPLUN : Lund code, particle code used in the Lund Monte — Carlo © PCHA UPCHA : particle charge - 71- DELSIM Vers 3.2 PTAU UPTALU:: particle lifetime PSPI UPSPI : particle spin PEURO UERO : particle code EUROJET The routine UPCON fills the common with the quantities for a given particle. A listing of the particles used inside DELSIM is found in appendix C on page C.1 . Users should call UPNAM (UPCON) to obtain the masses, and not define them explicitly in their code. Furthermore, the most readable and safest way to proceed, is to define the particle name in their routine ( in a data or param- eter statement ), and use UPNAM (UPCON) to get other particle information, as the mass codes might still change in the future. CALL UPNAM (‘particle name’) See appendix C on page C.1 or , CALL UPCON (‘code name’ ,value) So, for instance,’ SUBROUTINE ... +CDE , UCPCON. CALL UPNAM ('E- '‘) (fill /UCPCON/ with e data) or CALL UPCON('PLUN',7.0) (Lund code 7 is for e™) Also, in order to check the identity of a given particle, it is best to make the test on the particle code (not on the mass value, which may be different on different computers or after writing the events out). Particles always have a positive mass code, antiparticles have the opposite value. The mass itself is identical for particles and their antiparticles. The particle code is always carried together with the other track variables. WARNING : There are particles which are defined in the LUND code but have not been (due to lack of characters) named in the DELPHI code. They keep the LUND code number + a con- stant (24) as the DELPHI name. 7.4 Track/Vertex labels and types In order to allow a unique identification of tracks they are given labels which are consecutive inte- ger numbers. The primary vertex has label=0. A secondary vertex gets the same label as the track which gave rise to it. | Vertices get the same type as their origin track. The following types are defined: The particle has not been followed = 0 The particle leaves the detector = ] The particle reaches stop layer (see SXTRAF) = 2 7 Note that to avoid problems, the arguments of UPNAM should always have 4 characters (even if they are blank) —- 7.2— DELSIM Vers 3.2 The particle reaches the maximum track length WwW Overshooting of the maximum number of spirals Il The track stops WM The track has a secondary process: delta ray AN bremsstrahlung ~I1 pair production CO Compton scattering OO decay pee pee © hadronic interaction HH peek peek positron annihilation il peek peek photoelectric effect pn pn shower in calorimeter hWN pmeh pmeh In addition, the tracks are given a type, which follows closely the convention for the return integer JFLOUT from the routine SXTRAF [2]. The track type 1s the vertex type number of the process that produced this secondary particle. 7.5 Naming conventions for DELPHI detector modules A name is associated to every detector for easy selection and association with the geometry described on the data base. The conventions are listed in table Table 1 on page 7.4 below. The short name is used to define subroutine calls, eg SVBEG, and the second letter is added when both a barrel and a forward detector of the same type exists, SRBEGF etc, see section 5.2 on page 5.1. The different levels in the data base are accessed via the IMEDI vector. The information is stored as: IMEDI(1) Material name (hollerith) eg. PB+* IMEDI(2) Number of detector levels ( < 11) IMEDI(3—N) = Level names (in hollerith) from the data base, e.g., HPC, etc... 7.6 Definition of material constants The basic material constants are kept in the data base and are read if a new material is hit in the tracking. The routine SXDCOM then computes all other material constants required. See DELSIM reference manual ref. [2]. In the Figure Figure 7 on page 7.5, there is a schematic view of the DELPHI detector, shown here for completness. — 73- DELSIM Vers 3.2. Table /: Naming conventions for Detector modules Name Detector module Short name INT interaction region BEA beam tube ! VD vertex detector < ID inner detector TPC TPC WH RIB barrel RICH (B) OD outer detector OW HPC barrel electromagnetic calorimeter mG COI coil + cryostat TOF TOF scintillator counter rr SPA empty space outside the coil | HAB barrel hadron calorimeter co co (B) MUB barrel muon identifier M (B) CAB cable region FCA end cap chamber A | RIF end cap RICH Da pb (F) SAT small angle tagger LUM luminosity monitor (VSAT) FCB end cap chamber B EMF end cap electromagnetic calorimeter PWM SCQ S.C. quadrupole BLK iron block close to the quadrupole HAF end cap hadron calorimeter oO (F) MUF end cap muon identifier M (F) HOF forward hodoscope — 7.4- DELSIM Vers 3.2 BARREL HADRON CAL. FORWARD EM “2 MIRRORS CAL - BARREL RICH || | FORWARD CHAMBERS | S.deal Sige B Figure 7: General view of one quadrant of the DELPHI detector. - 7.5- DELSIM Vers 3.2 Appendix A SUMMARY OF DELSIM CONTROL CARDS The default values given are set in the subroutine SXDATA at initialization. They can all be modified via the corresponding control card. Key N Type Short description Common Default Input /output IDTIN I Controls FZIN of event SXCWRD IDTIN = 0 no input IDTIN = 1 rd evts w/ FZIN native mode from disk IDTIN = 2 rd evts w/ FZIN native mode from tape IDTIN = 3 rd evts w/ FZIN exchange mode from disk IDTIN = 4 rd evts w/ FZIN exchange mode from tape IDTIN= 5 rd evts w/ FZIN alpha mode from disk IDTIN= 6 rd evts w/ FZIN alpha mode from tape IDTOUT I Control the output of event data SXCWRD IDTOUT=0 no output IDTOUT= 1 wrt evts w/ FZOUT native mode on disk IDTOUT = 2 wrt evts w/ FZOUT native mode on tape IDTOUT= 3 wrt evts w/ FZOUT exchange mode on disk IDTOUT= 4 wrt evts w/ FZOUT exchange mode on tape IDTOUT= 5 wrt evts w/ FZOUT alpha mode on disk IDTOUT= 6 wrt evts w/ FZOUT alpha mode on tape IDLUIN I Input unit for external LUND common SXCIO IDLUIN= 0 no reading IDLUIN = 1 read from unit I ~ IDLUUT I Output unit to write LUND common SXCIO IDLUUT = 0 no writing IDLUUT= 1 write on unit I IPRNT Standard print unit pmenlh prem SXCIO IREAD Standard input unit pen SXCIO ITOUT ph Output unit to write if IDTOUT ne 0 pment SXCIO 21 ITIN «peek peneh Input unit to read if IDTIN ne 0 SXCIO 11 | LUNDBZ pemesh Unit for writing/reading preloaded data base SXCIO 59 LEUDAT Unit for EURODEC decay table eh SXCIO 35 LEUTIT Unit for EDRODEC Title file SXCIO 36 ITPLT Unit for Plotting output SXCIO 14 LOUTAN femdom pomodoro Output unit for TANAGRA SXTANA 30 Interface to fast simulation JFAST Switch to be put TRUE when running fast simulation SXPFAS —- Al - DELSIM Vers 3.2 Graphics output for DELGRA JTETS Flag to switch on graphics output for DELGRA SATETS Debug control IFEVDB First event with debugging printed output pet SXCDEB ILEVDB Last event with debugging printed output pet SXCDEB ISWIDB fe Array of switches to control the debug SXCDEB switches can be set to 0, 1 or 2 to select nodebug, minimum level debug or detailed debug ISWIDB(1) debugging of the generation ISWIDB(2) debugging of the tracking ISWIDB(3) debugging of the secondary processes ISWIDB(4) (used internally formodule debugging) MDB1 Names of modules selected for debug level 1 MDB2 Names of modules selected for debug level 2 MDB3 Names of modules selected for debug level 3 IZEBDB “Se IZEBDB = 1 DZSURV from LTOP = 2 DZSHOW from LTOP Tanagra output control IDTANA pond Type of Tanagra structure to be output SXTANA IDTANA = 0: no calls to TANAGRA routines IDTANA = 1: write VETBAS in native mode on disk IDTANA = 2: write VETBAS in native mode on tape IDTANA = 3: write VETBAS in exchange mode on disk IDTANA = 4: write VETBAS in exchange mode on tape IDTANA = 5: write VETBAS in alpha mode on disk IDTANA = 6: write VETBAS in alpha mode on tape LABO Laboratory identifier (see TANAGRA manual) SXTANA Random numbers ITEST Print ISEEDG and ISEEDS every ITEST event SXCRAN ISEEDG pone Random seed number for generation SXCRAN ISEEDS Random seed number for simulation SXCRAN List and history of particles JFLGSH os Build the history banks SH if = TRUE SXSHFL JFLPRM Print DELPHI and LUND particle SXPMAS JFLGLU Build up the LUJETS from the ZEBRA input data SXFLLU TY Steering of the tracking TRKLMX —" Maximum ps) track length: when the track length SXCDET 1000. exceeds TRKLMxX the tracking stops SPIRMX Maximum number eek of spirals SXCDET oni STEP Starting value of step size (cm) or SXCTRK STEPM ri ehfeh Maximum step size (cm) SXCTRK XLMIN ri Precision pmh on the length, minimum step size (cm) SXCTRK 0.1 DPMAX Ti Maximum fmh value of (dp/p) over a step SXCTRK 0.01 PMINH T) Minimum pom track momentum (GeV/c) for all particles SXCTRK 0.1 except for electron and positron PMINE ps 7 Minimum track momentum for electron and positrons SXCTRK 0.1 PMIN 1s set to PMINH or PMINE in SXPMIN — A.2- DELSIM Vers 3.2 called from SXTRAF DTMAX Maximum magnetic field error over a step SXCTRK TLMAX 0.01 a Maximum value of total SXTACK length SXCTRK 1000. the (used to control field variation over a step) TLMAX is never used to stop the tracking RATMIN Minimum fem value of ( 1.—length/TLMAX ) SXCTRK FRACLE 0.001 ped Fraction of potential length taken for SXCTRK 0.95 first step in SXTRAF Set higher for neutrals and when tracking in light media as vacuum or air STEPMD Maximum fered step acceptable from distance calculation SXCTRK 15.0 DPREC mend Precision (%) in distance calculation SXCTRK IDST 1.0 fmmed band ON/OFF flag for use of distance prediction SXCTRK IDST = 1 for distance prediction IDST = 0 for no distance prediction Database and detectors to be considered IRUN — Run number in database to be loaded SXCDAT NLEV \) Default geometry and sensing device level SXCDAT NLEV(1) = Default value for geometry loading + 1000, when sensing devices file selected NLEV(2) = Default value for calibration files DDDAT Date and time of the record to be loaded SXCDAT (0= without time dependence, 1=with time dependence) DDDAT(1) = date as YYMMDD 890401 DDDAT(2) = time as HHMMSS 120000 MSTP Modules for which tracking stops SXMSTP MSIM Modules for which detailed simulation is done SXMSTP MTRS Modules for which PA vectors to PSS be stored SXDDML WDBZEB Wnite out ZEBRA pk copy of data base store SXDDML F LDBZEB Read in ZEBRA pt copy of data base store SXDDML F IDDFZI pret Input data base store unit SXDDML 59 IDDFZO peek Output data base store unit SXDDML 59 IDDOVE Checks geometrical bk shapes overlaps 0 IDDVTY Unit TTY for data base bond diagnostic 3 IDDVPR Print unit for data base diagnostics bot SXCIO IPRNT Control of secondary processes (1 = active, 0 = inactive) JDRAYS peeeth Delta ray : pa | SXCACT JBREMS fpmeamh Bremsstrahlung pen SXCACT JPAIRS Pair production pam SXCACT JCOMPT fences Compton scattering meme SXCACT JDECAY Decay psec SXCACT JHAINT Hadronic interaction fom SXCACT JANNIH omer Positron annihilation fromm SXCACT uch JPHOTO ome] Photoelectric effect SXCACT ITMULS paves Controls the multiple scattering pave SXCTRK = 0: no multiple scattering = 1: simulate multiple scattering = 2: compute multiple scattering matrix = 3: simulate multiple scattering (Moliére) Control of titles - A3- DELSIM Vers 3.2 NMEDMX 1 Maximum pound number of media in titles SXCTAB 100 NCONMX 1 Maximum number of constants pwnd for a given medium SXCTAB 100 Event generation or simulation IGENER Controls which generator to use (see chapter 2) SXCWRD 1 ISIMUL Controls the simulation SXCWRD 2 ISIMUL= 0 no simulation ISIMUL= 1 simulation without secondary processes but with multiple scattering ISIMUL= 2 simulation with secondary processes NEVMAX Number of events to process SXCNEV 10 IEV1 punad Initial event no., when reading from ITIN Particle life times and TOP quark mass VTAU 128 Lifetimes for DELSIM particles SXPDBL AMTOP Top quark mass, also used for calculating GSW SXCILP 30. Storage of short living particles kinematic JSHORT = TRUE if one want the SP and ST structure SXDECF already in the generation part of the program NSDECY Number of particles for JIDECY SXSDEC 10 JSDECY List of particles (DELPHI code) SXSDEC for which SP and ST banks are created if JSHORT=TRUE Defaults are :10 = TAU, 44 = D0, 45 = D+, 46 = FH, 82 = LA+, 83= CSU00+, 84 = CSD00, 125 = BU,126 = BD, 127 = BS Lifetimes are coming from DELPHI lifetime list Constants for the standard electroweak model IZ1LOP controls how the GSW parameters are computed SXCWRD IZILOP=0 using CONMZ and SSQT, with no radiative corrections = 1 using AMZ, AMTOP, AMHIGS, with 1—loop GSW XNFAMS Number of parton families SXCQFI SSQT pen Sin(THETA)+*2 in SU(2)*U(1) SXCQFI 0.22 CONMZ Constant to compute Z0 mass pwd SXCQFI 37,281 AMZ ZO mass used in calculation of GSW parameters SXC1LP 92. AMHIGS Higgs mass used in calculating GSW parameters SXCILP 100. AMTOP Top quark mass, also used for calculating GSW par. SXCILP 30. Initialisation of the beam parameters EBEAM rane Mean value of beam energy SXCBEA DEBEAM Spread on the beam energy pomed SXCBEA IBEAM Selects energy distribution: SXCBEA IBEAM = 1 gaussian, = 2 constant XYZW Spread of interaction point (gaussian in 3- dim) SXCBEA Steering of the fragmentation: Lund Monte Carlo JGLU Controls the gluon generation SXCGEN JGLU=0 no gluons — A4- DELSIM Vers 3.2 JGLU= 1 generate gluons MSTE 40 LUND steering (see LUND Monte Carlo writeups) LUDATE Default MSTE(4) = 6 __, 6 quarks PARE 80 LUND steering (see LUND Monte Carlo writeups) LUDATE MST 40 LUND steering (see LUND Monte Carlo writeups) LUDATI1 PAR 80 LUND steering (see LUND Monte Carlo writeups) LUDATI1 PMAS 120 LUND steering (see LUND Monte Carlo writeups) LUDAT2 Default PMAS(106) = Top quark mass of DELSIM IDB 120 LUND steering (see LUND Monte Carlo writeups) LUDAT3 Default: prevent some particles from decaying in Lund by IDB(n)=0( 37 = KOs, 43 = SI+, 45= SI- , 57 = L0) Steering of the fragmentation: EUROJET Monte Carlo EUROFR Flag for EUROJET fragmentation SXCEUF LEUDAT meen Unit for EURODEC decay table SXCIO LEUTIT Unit poner for EURODEC Title file SXCIO B° — B® oscillations BDOS To activate B°d oscillations BSOS et To activate B°s oscillations XD Value of the xd parameter XS Value of the xs parameter MODOSC mT Define the mode of oscillation generation Generator IGENER=1 ( ete” + Z°/ y + qq /1*I- ) IFIXEN a Generation at fixed energy SXCZZ1 JPSEL Lepton/quark selection array : SXCZZ1 = 0 means not to generate , = 1 means to be generated Convention for particles in the JPSEL array : =nue S= numu 9= nutau 2=e 6= mu 10= tau 3=u 7= Cc ll=t 4=d 8= § 12= b Generator IGENER= 2 (ete > Z° > Z° H® > qq /I*I- ) XMH H° mass SXCHZ1 10.0 JPSELH 12 pound Lepton/quark selection for HO decay : SXCHZ]1 all 1 JPSELZ 12 Lepton/quark selection for Z0 decay : SXCHZ1 all 1 Convention for particles in the arrays as for JPSEL Generator IGENER = 3 (eve > Z°/fy > HtH” => qq/I‘l ) XMH1 Higggs mass SXCHH1 10.0 JPSLHP 12 Lepton/quark selection for H+ decay : SXCHH1 all 1 JPSLHM 12 Lepton/quark selection for H— decay : SXCHH1 all 1 Convention for particles in the arrays as for JPSEL Generator IGENER=4 ( ete” > y+y > qq /I*I- ) JSEL ] 0 no vertex modification, 1 for heavy e exchange : SXCGAM XLAMC ] QED cut off parameter SXCGAM 100.0 - AS- DELSIM Vers 3.2 CTLOW 1 Minimum cos(theta) SXCGAM 0.0 CTHIGH ] Maximum cos(theta) SXCGAM 0.99 Generator IGENER = 5 (single particles) NFEWPA l Number of particles to generate (max 10 default) SPNAME 10 particle names SXCSIP GAMM SPPMIN 10 minimum particle momentum in GeV/c SXCSIP SPPMAX 10 nape maximum particle momentum in GeV/c SXCSIP 10. SPTHMN 10 minimum theta degrees SXCSIP 20. SPTHMX 10 maximum theta degrees SXCSIP 160. SPPHMN 10 minimum phi degrees adda SXCSIP SPPHMX 10 maximum phi degrees SXCSIP 360. SPXMIN 10 minimum X cm SXCSIP SPXMAX 10 maximum X cm SXCSIP SPYMIN 10 AANA minimum Y cm SXCSIP SPYMAX 10 maximum Y cm SXCSIP SPZMIN 10 minimum Z cm SXCSIP SPZMAX 10 1AM maximum Z cm SXCSIP oofoosoD Generators IGENER= 11 (e*e7 > Z°/y sq sq ) JPSLSQ -Squark selection array : SXCSUS see = 0 means not to generate , = | means to be generated matrix Convention for particles in the JPSLSQ array : l= 0 5= 0 9= 0 2= 0 6= 0 10= 0 3= 1 = usq 7= 1 = csq 11l=1 = tsq 4= 1 = dsq 8= 1 = ssq 12=1 = bsq SQMASS 12 squark mass array : SXCSUS see Convention for particles in the SQMASS array : matrix l= 0. S5= 0. 2= 0. 6= 0. 3= 40. = usq mass 7= 100. = csq mass 4= 40. = dsq mass = 100. = ssq mass 9= 0. 10= 0. 11= 100. = tsq mass 12= 100. = bsq mass PHMASS photino mass SXCSUS GLMASS gluino mass SXCSUS IDMSQ puound 1 for sq > q + photino SXCSUS 2 forsq—>q + gluino Generator IGENER= 13 (ete~ > Z°/y sl sl) JPSLSI 12 squark selection array : SXCSUS see = 0 means not to generate , = | means to be generated matrix Convention for particles in the JPSUSL array : l= 0 = 0 9= 0 2= 1 = sel 6= 1=smu__ 10= 1 = stau 3= 0 7= 0 ll=0 4= 0 8= 0 12= 0 SLMASS 12 squark mass array : SXCSUS see Convention for particles in the SLMASS array : matrix 1= 0. 7= 0. 2= 30. = sel mass 8= 0. —- Ao- DELSIM Vers 3.2 3= 0. 9= 0. 4= 0. 10= 100. = stau mass 5= 0. ll= 0. 6= 30. = smumass 12= 0. _ ZINMSS zino mass | SXCSUS 40. Generator IGENER = 14 (ete” > f f(y )) IBHABH controls how ete~ + ete~ (y )is generated SXCBAB 0 IBHABH=0 using MUSTRAAL, ignoring t — channel = 1 with Bhabha generator THEMIN —" minimum scattering angle for IBHABH= 1 in degree SXCBAB 15. THEMAX maximum scattering angle for IBHABH= 1 in degree SXCBAB 165. —- A.7— DELSIM Vers 3.2 Appendix B ZEBRA BANKS FOR GENERATION [SIMULATION B.1 TOP — bank BANK TOP : TOP bank for the DELPHI ZEBRA structure NL= 5, NS=5 , ND= 1 Links : 0 not used —1l RAW raw data header bank —2 not used in simulation (except for start of run record) —-3 not used in simulation —-4 not used in simulation —35 SE simulation header bank —6 Trigger data —7 Saves PA vector for modules Data: 1 “TOP’ Bits : not used B.2 RAW — bank The links to the different module header data banks (RAWH) are defined in the BLOCKDATA MODBLO and are not necesary for the user to know. The steering of this is done in the routine SXWRAW and the corresponding routine in the data analysis program. BANK RAW : Header bank for the raw data NL= 21, NS= 21 , ND=0 Links : 0 not used —6 RAW data bank for Vertex Detector —7 RAW data bank for Inner Detector —-8 RAW data bank for TPC —9 RAW data bank for barrel RICH -10 RAW data bank for Outer Detector —11 RAW data bank for HPC —12 RAW data bank for Time Of Flight —13 RAW data bank for barrel Hadron Calorimeter —14 RAW data bank for barrel Muon detector -15 RAW data bank for FCA —16 RAW data bank for forward RICH - Bl - DELSIM Vers 3.2 —17 RAW data bank for Small Angle Tagger —-18 RAW data bank for FCB —19 RAW data bank for forward Electromagnetic Calorimeter —20 RAW data bank for forward Hadronic Calorimeter —21 RAW data bank for forward Muon detector —22 RAW data bank for Luminosity Monitor Data: B.3 Partition Master Bank BANK PMB : Partition Master Bank for a detector module R’module’, e.g., RHPC NL= 5, NS= 5 , ND=1 Links: 0 not used —] | error —2 | trigger 1 and 2 —3 | trigger 3 —4 | trigger 4 —§ | Raw data Data: B.4 SE— bank Definition of the units : distance in cm and energy in GeV BANK SE: Header bank for the Structure of the generated event NL= 4, NS= 4 , ND= 13 Links : 0 not used —] SP ( primary vertex ) —2 SP ( all secondary vertices ) —3 SI header bank for the generation history —4 SH history banks Data : l event number 2 mass ) 3 Px ) ofet 4 Py ) beam in lab frame 5 Pz ) mass ) Px ) ofe™ Py ) beam in lab frame Pz ) - B2- DELSIM Vers 3.2 10 Energy in the CMS ( = ete effective mass ) ll x) 12 y ) of interaction point 13 z ) Bits : not used B.5 SP — bank Definition of the units : distance in cm and energy in GeV BANK SP: vertex data, space point NL= 2, NS=1, ND=6 Links : 0 next SP (=0 if primary or last SP of secondaries) -1 ST —2 parent ST (for a secondary vertex only) Data : vertex type KN x ) WD y ) coordinates of the vertex BR Zz) am vertex label WN time in ns Bits : not used The convention for labels and types is given chapter 6. B.6 ST — bank Definition of the units : distance in cm and energy in GeV BANK ST: Simulated Track quantities in the lab frame NL=5, NS=1, ND= 13 Links : 0 next ST (=0 if last ST of the vertex) -1 SX —2 SP, start of the track —3 SP, end of the track —4 SI, parent —-5 SH Data : ] particle mass code (DELPHI convention) 2 Px (quantities defined at the start vertex) 3 Py 4 Pz 5 E — B.3- DELSIM Vers 3.2 ON P charge (in units of proton charge) COs] particle mass value 9 mass code of parent particle (DELPHI convention) 10 track label 1] track length (negative if incoming track) 12 track type 13 line number in LUND common Bits : 2 bremsstrahlung photon from initial e+ or e~ Note: — at secondary vertices, the incident track is also kept. Its momentum vector is such that the track is leaving the vertex and the track length is negative. — the convention for labels and types is given in chapter 6. B.7 SX — bank Definition of the units : distance in cm and energy in GeV BANK SX: Momentum and coordinates for the track at entrance of detector modules. NL= 1, NS= 1 ND= 10 Links : 0 next SX (=0 if last SX of the track ST) Data : Detector index (see ref _) Px Py Pz E P x AOIDNAWNHE y Z ODM poend lenght in the detector B.8 SI — bank Definition of the units : distance in cm and energy in GeV BANK SI: reference frame for a primordial Simulated Interaction NL= 4, NS=2, ND= 11 Links : 0 next SI —1 SI down —2 free (could support the history) —3 SI, parent —4 SE, backward link — B4- DELSIM Vers 3.2 Data : 1 identifier for the simulation (see below) 2 mass ) 3 Px )_ ofthe system 4 Py ) (defines Lorentz transformation 5 Pz ) to the up SJ) 6 E ) 7 Py) 8 cos(Theta) jet production angle in the rest frame 9 Phi jet production angle in the rest frame 10 particle 1 (code in Delphi convention) 1] particle 2 ” * * Bits : not used Q(LSI+1)= 0. unspecified physical system (e.g. H® Z° or H+ H-) l.e*e~ system from the beam definition 2.e*e~ system after emitting a bremsstrahlung photon 3. 1 Ibar system _ 4. q qbar system B.9 SH — bank Definition of the units : distance in cm and energy in GeV BANK SH: — Simulation History bank from the generation NL= 4, NS=0, ND= 11 Links : O next SH —1 SH, daughter particle —2 SH, mother particle —3 SH, sister particle —-4 ST Data : 1 particle mass code (DELPHI convention) 2 particle mass value 3 px ) 4 py ) 5 pz ) 1n laboratory system 6 E ) 7 P ) 8 charge 9 index in LUND common 10 K(,1) = 10000 * KS + KH (LUND convention) 11 KF(LUND) Bits : not used — B.5- DELSIM Vers 3.2 Appendix C PARTICLE DATA TABLE Some of the heavier particles in the table have no mass defined, since these masses will be defined by the given fragmentation programs (Lund or Eurodec). The listing of the particle data table can be obtained by setting the flag JELPRM = TRUE in the data cards file. That listing will also give the LUND table (not given here). PARTICLE CODE NAME LUND MASS CHARGE MEAN SPIN CODE LIFE NEUTRINO NUE 8 0.0000 0 0.100E+09 1/2 NUEB —8 0.0000 0 0.100E+09 1/2 ELECTRON E —_— 7 0.0005 ] 0.100E+09 1/2 E+ —7 0.0005 I 0.100E+09 1/2 UP U 501 0.3000 0 0.000E+00 1/2 UBAR — 501 0.3000 0 0.000E+00 1/2 DOWN D 502 0.3000 0 0.000E+00 1/2 DBAR — 502 0.3000 0 0.000DE+00 1/2 NEUTRINO NUMU 10 0.0000 0 0.100E+09 1/2 NUMB —10 0.0000 0 0.100E+09 1/2 MUON MU — 9 0.1060 —] 0.220E—-05 1/2 MU + —9 0.1060 1 0.220E—-05 1/2 CHARM C 504 1.6000 0 0.000E+00 1/2 CBAR — 504 1.6000 0 0.000E+00 1/2 STRANGE S 503 0.5000 0 0.000E+00 1/2 SBAR — 503 0.5000 0 0.000E+00 1/2 NEUTRINO NUTA 12 0.0000 0 0.100E+09 1/2 NUTB —12 0.0000 0 Q.100E+09 1/2 TAU TAU — 11 1.7840 —1 0.330E-—12 1/2 TAU+ — 11 1.7840 I 0.330E—12 1/2 TOP T 506 30.0000 0 0.000E+00 1/2 TBAR — 506 30.0000 0 0.000E+00 1/2 BEAUTY B 505 5.0000 0 0.000E+00 1/2 BBAR — 505 5.0000 0 0.000E+00 1/2 NEUTRINO NUCH 14 0.0000 0 0.100E+09 1/2 NUCB —14 0.0000 0 0.100E+09 = 1/2 CHI CHI-— 13 30.0000 —]1 0.000E+00 1/2 CHI+ —13 30.0000 ] 0.000E+00 1/2 HIGH H 508 80.0000 0 0.000E+00 1/2 HBAR — 508 80.0000 0 0.000E+00 1/2 LOW L 307 40.0000 0 0.000E+00 1/2 LBAR — 307 40.0000 0 0.000E+00 1/2 Photino PINO 93 2.0000 0 0.100E+09 1/2 - C1 - DELSIM Vers 3.2 Z—ino 18 ZINO 150.0000 0 0.000E + 00 1/2 W —ino 19 WIN + 150.0000 ] 0.000E + 00 1/2 —-19 WIN — 150.0000 —1 0.000E + 00 1/2 Gluino 20 GINO 8.0000 0 0.000E + 00 1/2 Photon 21 GAMM 0.0000 0 0.100E + 09 Z ZERO 22 Z0 93.0000 0 0.000E + 00 W BOSON Wt 82.0000 1 0.000E + 00 82.0000 —1 0.000E + 00 LL, GLUON 24 GLU 0.0000 0 0.100E +09 SNU elec 25 SNE 20.0000 0 0.100E + 09 — 25 SNEB 20.0000 0 0.100E + 09 Selectr. 26 SEL— 20.0000 —] 0.000E + 00 OC OL — 26 SEL+ 20.0000 1 0.000E + 00 Up sq 27 USQ 40.0000 0 0.000E + 00 — 27 USQA 40.0000 0 0.000E + 00 COCO Down sq 28 DSQ 40.0000 0 0.000E + 00 — 28 DSQA 40.0000 0 0.000E + 00 OO SNU muon 29 SNM 100 28.0000 0 0.100E + 09 — 29 SNMB — 100 28.0000 0 0.100E + 09 CC SMUON 30 SMU-— 100 28.0000 — I 0.000E + 00 — 30 SMU+ — 100 28.0000 1 0.000E + 00 Charm sq 31 CSQ 150.0000 0 0.000E + 00 — 31 CSQA 150.0000 0 0.000E + 00 OOOO Str sq 32 SSQ 150.0000 0 0.000E + 00 — 32 SSQA 150.0000 0 0.000E + 00 SNU tau 33 SNT 40.0000 0 0.100E + 09 OCC — 33 SNTB 40.0000 0 0.100E + 09 Stau 34 STA— 150.0000 a 0.000E + 00 — 34 STA+ 150.0000 0.000E + 00 OOO Top sq 35 TSQ 150.0000 0 0.000E + 00 —35 TSQA 150.0000 0 0.000E + 00 Bot sq 36 BSQ 150.0000 0 0.000E + 00 — 36 BSQA 150.0000 0 0.000E + 00 HIGGS 0 37 CO Oo HIGO 15.0000 0 0.000E + 00 eO HIGGS + 38 HIG+ 20.0000 Il 0.000E + 00 — 38 HIG-— 20.0000 —1 0.000E + 00 CSCO 39 DEUT 1.8756 I 0.000E + 00 — 39 TRIT 1.8756 —1 0.000E + 00 40 ALFA 3.7274 2 0.000E + 00 Pion 4] PI+ 0.1400 I 0.260E — 07 — 41 PI- 0.1400 —] 0.260E — 07 Kaon 42 K+ 0.4940 1 0.124E — 07 — 42 0.4940 —1 0.124E — 07 K ZERO 43 KO 0.4980 0 0.000E + 00 — 43 KBO 0.4980 0 0.000E + 00 D ZERO DO 1.8650 0 0.430E — 12 DBO 1.8650 0 0.430E — 12 D MESON 45 D+ 1.8690 0.920E — 12 — 45 1.8690 —] 0.920E — 12 DS MESON 46 DS 1.9720 0.280E — 12 46 DS B 1.9720 1 0.280E — 12 F MESON 46 F+ 1.9710 l 0.280E — 12 PesesggesesseeorrKKH — 46 1.9710 —1 0.280E — 12 PI ZERO 47 PIO 0.1350 0 0.830E — 16 Ce DELSIM Vers 3.2 ETA 48 ETA 24 0.5490 0.100E— 18 ETA P 49 ETAP 25 0.9580 0.000E + 00 ETA CHAR 50 ETAC 26 2.9810 0.000E + 00 RHO 51 RHO+ 2/ 0.7660 0.000E + 00 —51 RHO-— —27 0.7660 0.000E + 00 K STAR 52 Ka + 28 0.8920 0.000E + 00 — 52 K+#B— — 28 0.8920 0.000E + 00 KO STAR 53 K+0 29 0.8980 0.000E + 00 — 53 K+*BO0 — 29 0.8980 0.000E + 00 DO STAR 54 D0 30 2.0060 0.000E + 00 — 54 D«BO0 — 30 2.0060 0.000E + 00 D STAR 55 Ds + 31 2.0100 0.000E + 00 —55 D+#B-— —3] 2.0100 0.000E + 00 DS STAR 56 DS» 32 2.1150 0.000E + 00 — 56 DS*B — 32 2.1150 0.000E + 00 RHO ZERO 57 RHOO 33 0.7700 0.000E + 00 OMEGA 58 OMEG 34 0.7820 0.000E + 00 PHI 59 PHI 35 1.0200 0.000E + 00 J—PSI 60 JPSI 36 3.0970 0.000E + 00 KO SHORT 61 KOS 37 0.4980 0.892E— 10 KO LONG 62 KOL 38 0.4980 0.518E—07 A1(1270) 63 Al+ 1.2750 0.000E + 00 — 63 Al- 1.2750 0.000E + 00 A1(1270) Al0 1.2750 0.000E + 00 PROTON 65 4] 0.9380 0.100E + 09 1/2 — 65 PB — 41 0.9380 0.100E + 09 1/2 NEUTRON 66 42 0.9400 0.918E +03 1/2 — 66 NB — 42 0.9400 0.918E +03 1/2 SIGMA + 67 S + 43 1.1890 0.800E — 10 1/2 — 67 SB- — 43 1.1890 0.800E — 10 1/2 SIGMA 0 68 S0 1.1920 0.580E—19 1/2 — 68 SBO 1.1920 0.580E— 19 1/2 SIGMA — 69 45 1.1970 0.148E—09 1/2 — 69 SB+ — 45 1.1970 0.148E —09 1/2 XI 0 70 X0 46 1.3150 0.290E — 09 1/2 —70 XBO0 — 46 1.3150 0.290E — 09 1/2 AI — 71 47 1.3210 0.164E—09 1/2 —71 XB+ — 47 1.3210 0.164E — 09 1/2 SIC + + 72 72 48 2.4400 0.000E + 00 1/2 —72 72B — 48 2.4400 0.000E + 00 1/2 SIC + 73 73 49 2.4400 0.000E + 00 1/2 —73 73B — 49 2.4400 0.000E + 00 1/2 SIC 0 74 74 50 2.4400 0.000E + 00 1/2 — 74 74B — 50 2.4400 0.000E + 00 1/2 CSU1 + 75 75 S1 2.5900 0.000E + 00 1/2 —75 75B —51 2.5900 0.000E + 00 1/2 CSD1 0 76 76 52 2.5900 0.000E + 00 1/2 — 76 76B — 52 2.5900 0.000E + 00 1/2 CSS1 0 77 77 53 2.7600 0.000E + 00 1/2 —77 77B — 53 2.7600 0.000E + 00 1/2 CCU1 + + 78 78 54 3.6300 0.000E + 00 1/2 —78 78B — 54 3.6300 0.000E + 00 1/2 CCD1 + 79 79 55 3.6300 0.000E + 00 1/2 -—79 79B —55 3.6300 0.000E + 00 1/2 - C3- DELSIM Vers 3.2 CCS1 + 80 = 80 56 3.8100 1 0.000E+00 1/2 —-80 80B — 56 3.8100 — I 0.000E+00 1/2 LAMBDA 0 81 LO 37 1.1160 0 0.263E—-09 1/2 —81 LBO — 37 1.1160 0 0.263E—-09 1/2 LAMC + 82 LC+ 58 2.2800 l 0.230E-—12 1/2 —82 LCB- — 38 2.2800 —] 0.230E—12 1/2 CSU0 + 83 At 59 2.5000 1 0.110E-12 1/2 —-83 AB-— —59 2.5000 —] O.110E—12 1/2 CSD0 0 84 AO 60 2.5000 0 O.110E—-12 1/2 —84 ABO — 60 2.5000 0 QO.110E-—12 1/2 DELTA + + 85 Ne++ 61 1.2300 2 0.000E+00 3/2 —85 Ne--—- — 6] 1.2300 —2 0.000E+00 3/2 DELTA + 86 Ne+ 62 1.2310 l v.000E+00 3/2 —-86 N*B- — 62 1.2310 —1 0.COOE+00 3/2 DELTA 0 87 N«0 63 1.2320 0 0.000E+00 3/2 —-87 N»«BO — 63 1.2320 0 0.000E+00 3/2 DELTA — 88 Ne— 64 1.2330 — I] 0.000E+00 3/2 —-88 N«B+ — 64 1.2330 1 0.000E+00 3/2 SIG« + 89 S#+ 65 1.3820 1 0.000E+00 3/2 —89 S*B- — 65 1.3820 —1 0.000E+00 3/2 SIG* 0 90 S«0 66 1.3820 0 0.000E+00 3/2 -90 S#BO — 66 1.3820 0 0.000E+00 3/2 SIG« — 91 S#- 67 1.3870 —] 0.000E+00 3/2 —91 S#*Bt+ — 67 1.3870 ] 0.000E+00 3/2 — XI« 0 92 X00 68 1.5320 0 0.000E+00 3/2 —-92 X*BO — 68 1.5320 0 0.000E+00 3/2 XI* — 93 Xe — 69 1.5350 —] 0.000E+00 3/2 -93 X*Bt+ — 69 1.5350 ] 0.000E+00 3/2 OMEGAs« — 94 OM- 70 1.6720 —] 0.130E-—09 3/2 -94 OM+ —70 1.6720 ] 0.130E—09 3/2 SIC* ++ 95 95 71 2.5000 2 0.000E+00 3/2 —-95 95B —71 2.5000 —2 0.000E+00 3/2 SIC* + 96 96 72 2.5000 l 0.000E+00 3/2 —96 96B —72 2.5000 —] 0.000E+00 3/2 SIC 0 97 97 73 2.5000 0 | 0.000E+00 3/2 —-97 97B — 73 2.5000 0 0.000E+00 3/2 CSUs + 98 98 74 2.6300 ] 0.000E+00 3/2 —98 98B — 74 2.6300 —] 0.000E+00 3/2 CSDs« 0 99 99 75 2.6300 0 0.000E+00 3/2 —-99 99B —75 2.6300 0 0.000E+00 3/2 CSS 0 100 ~=—-:100 76 2.8000 0 0.000E+00 3/2 -100 100B — 76 2.8000 0 0.000E+00 3/2 CCUs ++ 101. 101 77 3.6900 2 0.000E+00 3/2 —-101 101B —77 3.6900 —2 0.000E+00 3/2 CCD« + 102. 102 78 3.6900 1 0.000E+00 3/2 | —-102 102B —78 3.6900 —1 0.000E+00 3/2 CCS* + 103-103 79 3.8500 ] 0.000E+00 3/2 —-103 103B — 79 3.8500 —1 0.000E+00 3/2 CCC+ ++ 104 =104 80 4.9000 2 0.000E+00 3/2 —-104 104B — 80 4.9000 —2 0.000E+00 3/2 ETA BEAU 107. ETAB 83 9.4000 0 0.000E + 00 0 ETA TOP 108 ETAT 84 38.9700 0 0.000E + 00 0 ETA LOW 109. ETAL 85 78.0000 0 0.000E + 00 0 ETA HIGH 110 ETAH 86 156.0000 0 0.000E + 00 0 - C4 - DELSIM Vers 3.2 UPSILON 111 UPSI 87 9.4600 0.000E + 00 PHI TOP 112 PHIT 88 39.0100 0.000E + 00 PHI LOW 113 PHIL 89 78.0000 0.000E + 00 PHI HIGH KEL 114 PHIH 90 156.0000 0.000E + 00 BU MESON mM 125 BU 101 5.2940 0.120E—11 — 125 BU B OO —101 5.2940 0.120E — 11 CO BD MESON 126 BD 102 5.2940 0.120E—11 — 126 BDB — 102 5.2940 0.120E — 11 BS MESON 127 BS 103 5.4800 0.120E—-11 OOD — 127 BS B — 103 5.4800 0.120E—-11 BC MESON 128 BC 104 6.5940 0.000E + 00 — 128 BC B — 104 6.5940 0.000E + 00 TU MESON 129 TU 105 0.0000 0.000E + 00 OOOO 129 TUB — 105 0.0000 0.000E + 00 eoC TD MESON 130 TD 106 0.0000 0.000E + 00 — 130 TDB — 106 0.0000 0.000E + 00 CoCo TS MESON 131 TS 107 0.0000 0.000E + 00 — 131 TS B — 107 0.0000 0.000E + 00 TC MESON 132 TC 108 0.0000 0.000E + 00 ocococo — 132 TC B — 108 0.0000 0.000E + 00 TB MESON 133 TB 109 0.0000 0.000E + 00 — 133 TBB — 109 0.0000 0.000E + 00 BU «— Coe 147 BU «x 123 5.3350 0.000E + 00 1/2 — 147 BU +B — 123 5.3350 0.000E + 00 1/2 BD «0 148 BD x 124 5.3350 0.000E + 00 1/2 — 148 BD *B — 124 5.3350 0.000E + 00 1/2 BS +0 149 BS » 125 5.5070 0.000E + 00 1/2 — 149 BS *B — 125 5.5070 0.000E + 00 1/2 BC *— 150 BC + 126 6.6020 0.000E + 00 1/2 — 150 BC *B — 126 6.6020 0.000E + 00 1/2 TU +0 151 TU 127 0.0000 0.000E + 00 — 151 TU «B — 127 0.0000 0.000E + 00 TD *+ 152 TD x 128 0.0000 0.000E + 00 — 152 TD *B — 128 0.0000 0.000E + 00 TS «+ 153 TS * 129 0.0000 0.000E + 00 — 153 TS *B — 129 0.0000 0.000E + 00 TC +0 154 TC * 130 0.0000 0.000E + 00 — 154 TC *B — 130 0.0000 0.000E + 00 TB *¥+ 155 TB x 131 0.0000 0.000E + 00 ~ 155 TB *B — 131 0.0000 0.000E + 00 BUUI+ 169 BUUI1 145 5.7950 0.400E — 12 — 169 BUUI1 — 145 3.7950 0.400E — 12 BDU10 170 BDU1 146 3.7950 0.400E — 12 — 170 BDU1 — 146 5.7950 0.400E — 12 HDoppyhperecoocooocco II BDD1- 171 BDD1 147 5.7950 0.400E — 12 1/2 —171 BDDI1 — 147 3.7950 0.400E — 12 bt BSU10 172 BSU1 148 5.9560 pre 0.400E — 12 NWN pand ~ —172 BSU1 — 148 5.9560 0.400E — 12 1/2 BSD1 173 BSD1 149 5.9560 0.400E — 12 1/2 —173 BSD1 — 149 5.9560 0.400E — 12 1/2 BSS1— 174 BSS1 150 6.1220 0.400E — 12 1/2 — 174 BSS1 — 150 6.1220 0.400E — 12 1/2 BCUI+ 175 BCU1 151 7.0370 0.400E — 12 1/2 —175 BCU1 — 151 7.0370 0.400E — 12 1/2 - C5 - DELSIM Vers 3.2 BCD10 176 BCDI1 152 7.0370 0 0.400E — 12 1/2 — 176 BCD1 — 152 7.0370 0 0.400E — 12 1/2 BCS10 177 BCS1 153 7.2110 0 0.400E — 12 1/2 —177 BCS1 — 153 7.2110 0 0.400E — 12 1/2 BCC1+ 178 BCC] 154 8.3090 ] 0.400E — 12 1/2 — 178 BCC] — 154 8.3090 a 0.400E — 12 1/2 BBU10 179 BBU1 155 10.4230 0 0.400E — 12 1/2 — 179 BBU1 — 155 10.4230 0 0.400E — 12 1/2 BBD1—- 180 BBD1 156 10.4230 —] 0.400E — 12 1/2 — 180 BBD1 — 156 10.4230 0.400E — 12 1/2 BBS1—-— 181 BBS1 157 10.6020 I 0.400E — 12 1/2 — 181 BBS1 — 157 10.6020 l 0.400E — 12 1/2 BBC10 182 BBC] 158 11.7080 0 0.400E — 12 1/2 — 182 BBC1 — 158 11.7080 0 0.400E — 12 1/2 BDU00 265 BDU0. 241 5.6160 0 0.400E — 12 1/2 — 265 BDUO — 241 5.6160 0 0.400E — 12 1/2 BSUO00 266 BSUO 242 5.8410 0 0.400E — 12 1/2 — 266 BSU0 — 242 5.8410 0 0.400E — 12 1/2 BSDO- 267 BSDO 243 5.8410 —] 0.400E — 12 1/2 — 267 BSDO — 243 5.8410 l 0.400E — 12 1/2 BCU0+ 268 BCUO 244 7.0060 ] 0.400E — 12 1/2 — 268 BCU0 — 244 7.0060 —I 0.400E — 12 1/2 BCDO00 269 BCDO 245 7.0060 0 0.400E — 12 1/2 — 269 BCDO — 245 7.0060 0 0.400E — 12 1/2 BCS00 270 BCSO 246 7.1910 0 0.400E — 12 1/2 — 270 BCSO — 246 7.1910 0 0.400E — 12 1/2 - C.6—- DELSIM Vers 3.2 Appendix D DEFINITION OF DECAY CONSTANTS The ZEBRA title for decay parameters. The decay constants use in DELSIM are: Particle Branching Decay Products Name Ratio MU — 0.986 NUMU NUEB MU + 0.986 E+ NUMB NUE PI + 0.000 MU+ NUMU PI- 0.000 MU -— NUMB PIO 0.9885 GAMM GAMM TAU — 0.1641 NUEB NUTA 0.1597 MU — NUMB NUTA 0.098 PI- NUTA 0.2301 RHO — NUTA 0.100 Al- NUTA TAU + 0.1641 E+ NUE NUTB 0.1597 MU + NUMU NUTB 0.098 PI + NUTB 0.2301 RHO+ NUTB 0.100 Al+ NUTB 0.6350 MU—- NUMB 0.2116 PI- PIO 0.0559 PI+ PI- PI-— K+ 0.6350 MU + NUMU 0.2116 PI+ PIO 0.0559 PI+ PI+ PI— KOS 0.6861 PI+ PI— 0.3139 PIO PIO KOL 0.215 PIO PIO PIO 0.1239 PI+ PI— PIO 0.271 PI+ MU— NUMB 0.387 PI+ E- NUEB LO 0.642 PI- 0.358 PIO LBO 0.642 PB PI+ 0.358 NB PIO S + 0.5164 PIO 0.4836 PI+ SB- 0.5164 PB PIO 0.4836 NB PI— 0.0000 PI- - Dl - DELSIM Vers 3.2 SB+ 0.0000 NB PI+ x0 0.0000 LO PIO 0.0000 LO PI-— OM — 0.686 LO 0.234 XQ PI- 0.080 PIO - D2- DELSIM Vers 3.2 Appendix E RUN EXAMPLES E.1 Run decks at CERN VXCRNA At the CERN vax VXCRNA the DELPHI program files exists on the [DPF...] directories. For the full simulation the programs are on the [DPF.SIM] area. The area is organized as follows: The DELPHI simulation PAM DELSIM32.CAR includes the generation and the general simu- lation routines. The different module pams are available as card pams with the name of the module like HPCSIM.CAR, TPCSIM.CAR, etc (except for the RICH which is called RICHALL, because the Delana code is included in the pam). The creation of libraries is done with the COM files: DELSIMLIB.COM witch creates the DELSIM standard library DELSIM32.OLB the changes to the DELSIM32 PAM or the different module pams are read from the cradles ; SIMCRA32.CAR MODCRA32.CAR In order to see what has been updated you can read the comments in the SIMCRA32.CAR and MODCRA32.CAR files. The library with the different module routines is created with the com file. MODSIMLIB.COM and the library is called MODSIM.OLB In order to get rid of unsatisfied externals in the case not all module routines exists a special “dummy” library is created by the com deck SIMDUMLIB.COM which produces the dummy library - E.l- DELSIM Vers 3.2 SIMDUM.OLB That library should be used when the graphics output to DELGRA is requested. The RUN deck for creation of the EXE files are: SIMRUN.COM for the standard version (see next section) The steering of a run can be done in the run card file: SIMRUN. TIT For the run decks there are three options: 1) without any parameters you compile and link and execute 2) with the parameter C you compile and link the program 3) with the parameter R you start executing direct and reading the runcards file e.g. SIMRUN R_ will execute the program and read the runcards file SIMRUN. TIT. In order to make your own runs you should copy the files SIMRUN.COM and SIMRUN.TIT to your area. Next section describes the run deck SIMRUN.COM on the VXCRNA. E.2 Create a EXE file on the CERN VXCRNA This appendix shows a run deck at the CERN VAX system. The deck has first a Patchy cradle with selection of the different opptions to create your EXE file. Then there are an example of an user routine for histogramming. In order to get down the size of the EXE files on the VAX a special option file LINKPROC.OPT is loaded at the end of the linking procedure. $ ecoddea odeo dG a AOE GSS SASS ES ASSO GORE dao oeieckok : $! 28/81/89 xk $! * $! This is the SIMRUN COM deck for DELSIM32 * $! This deck is prepared for new users who need to modify some of the x $! routines. It includes a Patchy run» the compilationsthe linking» x 3! the assignment of files and the execution. * $! The ZEBRA output can be used as the input to the DELPHI * $! analysing package DELANA. * $! * $! It uses the PAM files and libraries of the DELSIM on the DPA.SIM * $! area and a preloaded data base (DATABASESTORE.DAT) which includes thex $! detailed detector description information for all modules. * $! * $! You need this com file and the SIMRUN.TIT file in your own area. * $! To do everything» from Patchy to execution» in one go you just type: x $! SIMRUN * $! * $! It is possible to run only part of the job steps of SIMRUN :; $! * SIMRUN C to run Patchy» compile and link * $! SIMRUN A to assign the files only | * $! SINRUN R- to assign the files and run the program * $! * $! If you want to modify the run conditions change the parameters in thex $! control card file SIMRUN.TIT. The contro! cards are defined in the x $! appendix A in DELSIM user’s guide (DELPHI 87-96 PROG-99). * $! * $! Good luck * $! Per Olof Huilth / Luc Pape * $!dogoooeccbekkke Start of commad cards for VAX version KR KKKRKER EEK $! The following assigns should be redefined for different computers : $ ASS DISKSDELPHI3: [OPA.SIM) SIM: — E.2- DELSIM Vers 3.2 $ ASS DISKSDELPHI3:(DPA. TAN) TAN: $ ASS DISKSDELPHIS3: [DPA.DET. DDAPP] DDAPP: $ ASS DISKSDELPHI3: [OPA.DET.OBBASP] OBBASP: $ ASS DISKSDELPHI3: [D0PA.DDB) DDB: $ ASS DISKSDELPHI3: [OPA.UTY) UTY: $ ASS DISKSDELPHIS: [EVTDEV. SIM) EVT;: S$ ASS DISKSSCRATCH: [DELPHI.WNEEK) SCRATCH: $! end of assiqn definition $ IF Pl .EQS. "R" THEN GOTO RUNX $ IF Pl .EQS. "A" THEN GOTO RUNX $ CREATE SIMRUN.CRA +OPTION> MAPASM. +RASM> 23. +USE> VAX, +USE> «MAIN. Compile MAIN routine in order to put in your own +USE> MAINCR. Select standard corrections in SIMCRA.CAR +USE> SXTITO. Activate decay title in DELSIM.CAR +USE,» HBOOK4. Activate HBOOKk +USE> DUMNOD. Activate dummy module routines in DELSIM.CAR +EXE. +USE>P=SXCEBR>» O=ZEND. Activate IF=HBOOK in ZEND SSELF. egsgogggdoooggogdidaidaioigaiagiooiaaiagiotioiocios OO GK +SELF. Do not select the dummy routines for the modules you want to load +SELF. from the MODSIM.OLB tibrary +SELF. The INHIBIT cards below will inhibit the dummy routines of the +SELF. modules to compiled in this Job» in such a way that the module +SELF. routines will be taken from the MODSIM library instead which +SELF. contains the "real" routines. +SELF ogo dd o og iaaogaic OOOO Gogo +USE> P=DUMMOD>D=VD>T=INHIBIT. Take VD routines from modtib +USE> P=DUNMNOD>D=I0>T=INHIBIT. Take ID routines from mod!lib +USE> P=DUMNOD,D=TPC> T=INHIBIT. Take TPC routines from modlib +USE> P=DUNMNOD»D=FCA> T=INHIBIT. Take FCA routines from modlib +USE> P=DUNNOD>D=FCB>T=INHIBIT. Take FCB routines from modlib +USE>» P=DUNNOD,D=0D>T=INHIBIT. Take O00 routines from modlib +USE> P=DUMMNOD>D=TOF>,T=INHIBIT. Take TOF routines from modlib +USE> P=DUMNNOD,D=HPC> T=INHIBIT. Take HPC routines from modlib +USE> P=DUNNOD>O=EMF>T=INHIBIT. Take EMF routines from modlib +USE> P=DUNNOD,O=RIB>T=INHIBIT. Take barrel RICH routines from modlib +USE> P=DUMMOD,O=RIF>T=INHIBIT. Take forward RICH routine from modlib +USE> P=DUMNMOD>D=NUB>,T=INHIBIT. Take MUB routines from modlib +USE> P=DUNMNOD>D=HAF,T=INHIBIT. Take HAF routines from modlib +USE> P=DUMMOD>O=HAB> T=INHIBIT. Take HAB routines from modlib +USE» P=DUNMOD,D=NUF>T=INHIBIT. Take MUF routines from modlib +USE> P=DUMNNOD>D=SAT> T=INHIBIT. Take SAT routines from modlib +S ELF dasa da aoc oa coodcioisikioigukakuiaakgoko GOK +KEEP> SXSIZEOQ. PARAMETER (LSIZEQ=798800>LSIZWS=198088) +KEEP>SXSIZET. PARANETER (ITSIZE =88888) +KEEP> DOSPACE, IF=-D0APP288. Standard for DDAPP396 - PRRAMETER (IDDSIZ = 788888, NFENCE = 28) CONMON/DDAPCM/ IDDSTO» IDDDIV, FENCE (NFENCE)» ISPDD(IDDSIZ) +PAM>LUN=11>T=HOLD>R=MAINCR. +PAM>LUN=12,T=ATTACH>C. SIM: DELSIM32.CAR +SELF. OK +PAM>»LUN=11,T=RESUME. +SELF. Insert USER new decks here. +DECK> USHIST. Be whe aE abe ak BEE EISELE EDEL. LLL ODS ARS OS AES OS OES AB AR. AR IR. XR OS AR AR OB IR OE IRR RO ORR KK a kk ok ak ok > * User subroutine for histogramming * * * * RETURN END +QUIT. $ NEWCERNLIB $ CERNLIB GRAFLIB/HNEW> GENLIB $ YTOBIN SIM:SIMCRA32 SIMCRA - - TTY .GO S$ YPATCHY SIMCRA SIMRUN SIMRUN TTY -~ SIMRUND - - -~ .C¢Q $ FOR SIMRUN S$ DELETE/NOCONF SIMRUN.FOR;x $ DELETE/NOCONF SIMCRA. PAN; * $ LINK/NOMAP SIMRUN- >» SIM: DELSIN32/LIB- > SIM: EURODEC/LIB- > SIM: MODSIM/LIB- > SIM: DELSIMN32/LIB- » UTY:UFTELD/LIB- » TAN: TANAGRA311/LIB- » SIM: SIMOUM/LIB- » DDAPP: DDAPP387/LIB- > USERSLIBRARY: JETSET/LIB- » DBBASP; OBBASP281/LIB>KAPACK288/LIB~- » ?LIBS’- >» UTY:LINKPROC/OPTIONS $ DELETE/NOCONF SIMRUN. OBJ; x $ PURGE SIMRUN.EXE $ DEL/NOCONF/LOG SIMRUN.CRA:x $ IF Pl .EQS. "C" THEN GOTO END $ RUNX: $ _ DB: 00BASS388 $ HSS SIM: DATABASESTORE.DAT FOR@SS ! Preloaded database S$ ASS SIM: SIMRUND.ASD FOR@@1 ! TITLE file (decay constants) $ ASS SIMRUN. TIT FOR@1S | xx YOUR control card file x $ ASS SIM: EURODEC. DAT FOR@3S ! EURODEC decay constants -— B3 - DELSIM Vers 3.2 ASS SIM: EURODEC.TIT FOR836 EURODEC TITLE constants ASS SIM:PEGSDAT.DAT WH FOR816 HPC simulation constants ASS NL: FOR821 cEBRA output unit ASS NL: FOR838 TANAGRA output unit ASS SYSSOUTPUT FOR883 ASS SYSSOUTPUT FORS84 =EBRA AAHHWH ASS SYSSOUTPUT FOR886 $! ASS SCRATCH: ZEBRA_ZMUG.DAT FOR@21! ZEBRA output file $ IF Pl .EQS. "A" THEN GOTO END $ RUN/NODEBUG SIMRUN $ END: $ EXIT E.3 Create a histogramming and plotting program in the VM In the EXEC file which follows is shown an example on how to run DELSIM on VM, where are also provided the modifications to an user histogramming routine USHIST. This example show how to create a metafile from the HBOOK plots, to be printed on 3812 printers. Here, one finds also an example on how to pass a parameter to the program, set by control cards, through the use of the SXUFEFR subroutine. /*xk* Job to run DELSIM.. (current version DELSIN32) KS /*x** Generate e+e- --> mu+mu-gamma events /*BATCH JOB EXAMPLE STOR 12N TIME 15:88 */ *GIME PUBXX 197 G (NONOTICE” *GINE UDISK U (NONOTICE’ DOO Input fi les Jedd Rodddobickioks kk / *FILEDEF 1 DISK SIMDEC DATA G (PERN? *FILEDEF 15 DISK STEER DATA x (PERM? *FILEODEF 23 DISK SOTDCS DATA G (PERM RECFM F LRECL 8@° *FILEDEF 16 DISK PEGSDAT DATA G (PERN RECFM F LRECL 89° *FILEDEF S8@ DISK DOSYSF DATA G (PERN? *FILEDEF Si DISK DODIRE DATA G (PERM? Nrec=qfile(’DDGEOM DATA G’,*RECNO’) "FILEDEF S2 OISK ODGEOM DATA G (PERM XTENT’ nrec Nrec=qfile(’DDCOMM DATA G’>’RECNO’) “FILEDEF S3 DISK DDCOMM DATA G (PERM XTENT’ nrec Dod Oooo: Output files sec OOK KK / *FILEDEF 3 DISK EXAMPLE LOGFILE A (PERM RECFM F LRECL 135 *FILEDEF 6 DISK EXAMPLE OUTPUT A (PERM RECFM F LRECL 8@° *FILEDEF 14 DISK SIMPLOT NETAFILE (PERM RECFM F LRECL 89° >FILEDEF 19 DISK DTBZCEB DATA G (PERM RECFM VBS BLKSIZE 6232 ” *YPATCHY DUMMY="" CRADLE="RUN CRADLE x" LISTING="PATCHY OUTPUT A”? 7VFORT ASM (NOMAP?’ *CERNLIB DELSIM32 MODSIM32 DDAPP387 DBBAS38B KAPAK288 TANAG311 UFIELD JETSET GENLIB GRAFLIB’ *SETSTOR 88” *LOAD ASM (NOMAP NOAUTO START? /*BEGIN RUN CRADLE RECFM F LRECL 88x/ +EXE. ae he Ee Ze ab ode he TOELF. ood oI GET ALL CDE’S x&x4 +KEEPs SXSIZEQ. PARAMETER (LSIZEQ=486888>LSIZNS=158888) +KEEP>SXSIZET. PARAMETER (ITSIZE=188) +KEEP>» DDSPACE. PARAMETER (IDDSIZ = 788888, NFENCE = 28) COMMON/DDAPCM/ IDDSTO,» IDODIV, FENCE +SELF. dock FOR HBOOK AND HPLOT xa +KEEP>SXCPAH. PARAMETER (CIHSIZE=15888) COMMON /PAWC/ HMEMOR(IHSIZE) +SELF. doko ADDING CUT PARAMETERS +KEEP,SXCUTS. COMMON /SXCUTS/ ANGCUT +USE>SXCDES>T=E. +USE>P=MAINCR»D=SXCDECH>T=E. Standard CDE corrections +PAN>11,T=A,C.SIMCRA32 CARDS G +PAMN>11,T=A>C.DELSIM32 CARDS G +SELF. kx ' ko (DEXACTIVATION OF DETECTORS :kskkkoK +USE>P=DUMMOD,D=VD> T=E. +USE>P=DUMMOD,D=10>T=E. +USE>P=DUNMOD,D=TPC>T=E. +USE>P=DUMMOD.0=00;T=E. +USE>P=DUMMOD>D=TOF,T=E. +USE>sP=DUMMOD>D=FCA>T=E. +USE>P=DUNMOD> D=FCB> T=E. +USE»P=DUMMOD> D=HPC> T=E. +USE>P=DUMMNOD>D=EMF>T=E. +USE>P=DUNMOD;>D=SAT>T=E. +USE>P=DUMMOD, D=HAB> T=E. +USE>P=DUMMOD; D=HAF, T=E. +USE>P=DUMNMOD,0=RIB>T=E. +USE>P=DUMMOD,D=RIF>T=E. +USE>P=DUMMOD>D=MUB>T=E. +USE>P=DUMMOD, D=NUF> T=E. — B.4- DELSIM Vers 3.2 +USE>P=DUMMOD> D=LUM> T=E. +SELF. adocekkaceacaa (DE)ACTIVATE DUMMY USER ROUTINES FOO +USE>P=DUMMIES»D=SXPLOT>TsE. +USE>P=DUMMIES>D=SPXDUM>T=E. +USE>P=DUMMIESsD=SXUDUM>T=E. +USE > P=DUMMIES; D=SXUSUM;> T=E. +USE>P=DUMMIES»D=USHIST> T=I. +USE>P=DUMMIES,D=SXEURO>T=E. +USE>P=DUMMIES,D=TANDUM,T=E. +5SELF. AAG oeaoF +USE>CHECKALL> T=E. +USE> IBM» *DDAP> T=E, Select *xDDAP. +USE> TANAGRA; T=E. Select TANAGRA version. +USE: %xMAIN> THE, +USE>MAINCR; T=E, Select standard corrections +USEs P=MAINCR» D=SXCDECH, T=I. Suppress standard CDE corrections +USE>HBOOK4;> T=E. (De)-activate HBOOK stuff +USE>HPLOT> T= kkk eee EERE EE TELEDeEseaanaat * TERE RK BK RF +CDE,SXCIO. +CDE>SXCPAW. CALL HLIMIT(-IHSIZE) +SELF>IF=HPLOT. CALL HPLINT(8) CALL HPLCAP(-ITPLT) +SELF. RETURN END +SELF>IF =HPLOT. ogo SoG ORK +DECK>SXHPLE. SUBROUTINE SXHPLE SES SESS SOSSCSSOSCCOSCCSO TCL TT ET TT Tee * +CDE>SXCIO. +CDE>SXCPAN. CALL HPLZ0ON(152515” °) CALL HPLOT(288,” °5° *5@) CALL HPLOT(282,* °,’ *,@) CALL HPLOT(283,” °,° »,8) CALL HPLOT(281,” ’5” *5@) CALL HPLZON(1,1>1>” *) CALL HPLEND RETURN END +DECK, USHIST. SUBROUTINE USHIST * * * User subroutine for histogramming x * Aecolinearity in e+e- --> mu+mu- gamma * * * Oe EEE EE NR ME TR RR ROR OR RICO +CDE, 2 = PIPARM. IOI Kk ok KK DELSIM Vers 3.2 +CDE> = SXCDEB. +CDE> = SXCENB. +CDE> = SXCWRD. +CDE> = UCPCON. +CDE> = SXCUTS. +CDE> = SXCLKS> Z =Q. HARACTER«68 TITLE DATA IINIT / 8 / IF CIINIT.NE. 8) GO TO 18 Initalize HBOOK KH CALL HBOOKL (288)’Angle Gamma/muon (smaller) ’> + 188,8.8,128.8,8.) TITLE=’Acol linearity in mu+mu~(deg) vs Energy(gamma) ’ CALL HBOOK2 (261+TITLE>188,ANGCUT>38.8, 188)8.8528.859.8) CALL HBOOKL (2825’Acollinearity of mu+mu- (degrees)’> + 188,ANGCUT,38.8,8.) CALL HBOOK1 (283,’Gamma Energy (GeV)’; + 188>8.8,58.858.) IINIT = 1 18 CONTINUE NTRACK=8 LSHGA=-1 & Find SE»SH>ST banks e CALL UKDATA (LSE>*SE °) IF (LSE.LE.8) GO TO 999 LSH = LQ(LSE - 4) CONTINUE IF (LSH.LE. 8) GO TO 38 JCOD=INT(OQ (LSH+1)) IF (JCOD.EQ.2) LSHE1 =LSH IF (JCOD.EQ.-2) LSHE2 =LSH IF (JCOD.EQ.6) LSHMUL=LSH IF (JCOD.EQ.-6) LSHMU2=LSH IF (JCQD.EQ.22) LSHZ8 =LSH IF (JCOD.EQ.21) LSHGA =LSH NTRACK=NTRACK+1 IF (NTRACK.GE.9) GO TO 38 LSH=LQ(LSH) GO TO 28 CONTINUE IF (LSHGA.LE.8) GO TO 339 PXMU1=0 (LSHMU1+3) PXMU2=Q (LSHNU2+3) PYMU1=0 (LSHMU1+4) PYMU2=0 (LSHMU2+4) P2MU1L=0 (LSHMU1+5) P2MU2=0 (LSHNU2+5) PMU1=0 (LSHNU1L+7) PMU2=0 (LSHMU2+7) PMGA=Q0 (LSHGA+7) PXGR=0 (LSHGA+3) PYGA=Q0 (LSHGA+4) PZGA=0 (LSHGA+5) COSDEL T=- (PXMUL&PXMU2+PYMUL&PYMU2+PZ2MU1 &PZMU2) /PMUL/PMU2 COSGAM1= (PXMUL&PXGA+PYMUL*PYGA+PZNU1*PZGA)/PMUL/PNGA COSGAN2= (PXGA*PXMUZ+PYGAxP YMU2+PZGA*PZMU2) /PMGA/PNUZ COSGAN=AMAX1 (COSGAM1,COSGAN2) DELTA=ACOS (COSDELT) OGDELTA=DELTA*188/PI1 DEL TAGA=ACOS (COSGAM) «188. 8/PI IF (OGDELTA.LE.ANGCUT) GO TO 999 CALL HFILL (288,DELTAGA>@.>1.) CALL HFILL (281,DGDELTA»PNGA»1.) CALL HFILL (282,DGDELTA;>8.51.) CALL HFILL (283,PMGA>8.,51.) $39 CONTINUE RETURN END +SELF 0 Tom OB RR ok ak KKKKKEKKKKS x + OR RRS Ok KKK +QUIT /xBEG IN STEER DATA RECFM F LRECL 8@x/ LIST C kex kK Maximum number of events to be generated ooo NEVMA X 18888 C be ake ok RoC OOK DEBUG SETTINGS ood dod IFEVD B 7896 ILEVD B 7911 ISHID B 18e@ C kx 4c RANDOM NUMBER SEEDS AND PRINT FREQUENCY sacks OKA ISEED G 12345 ISEED S 12345 — E.6 - DELSIM Vers 3.2 ITEST 2888 C sad ggdongdddbiobkoobckobk BEAM ENERGY ooo EBEAM 46 C Sposa ogg agaRiot EVENT GENERATION 2a gGgoEd aa azGR C--- Choose process IGENER 14 C--- Simulation with secondaries ISIMUL 8 C Sedcpodoododooccek PARAMETERS FOR IGENER= 1 OR 146 doo Ok C--~ Select decay modes of the Z8 C nue eu dnum mucs nut tau tb JPSEL 8 888 8B 188 8 8 88 Coo Roo USER DEFINED CUTS xa:kaOKS ook Caro ( WARNING: Not standard in DELSIN Dass OOF Qleeccciokk ( Read through user defined SXUFFR) aasaesocuceodoK OE C-~- Cut in the accolinearity angle (in degrees» default is 1.8 degree) ANGCUT 18.8 _Qpdepoacoddoddocieaooaocooc: 1/0 DEFINITIONS aseouecuscooecacooiccs KK C-- Standard input and output units TREAD 1 IPRNT 6 C-- Write (NDBZEB) or Load (LOBZEB) the database to/from unit LUNDB2 WDBIEB FALSE LOBCEB TRUE LUNOBZ 19 C-- Get event from input (1) or generate event (8) from unit ITIN IDTIN 8 ITIN ll C~~ Output the raw data at unit ITOUT IDTOUT 8 ITOUT 21 C-- TANAGRA output at unit LOUTAN LABO >CERN’ IOTANR 8 LOUTAN 38 C -- Plot metafile data at unit ITPLT ITPLT 14 C lesa c added dco assoc OS SH Sgn Faiob i dtaioioiaaiaai ai i uaa ca aE TLIMIT 18, END JFLPRM FALSE END E.4 Example on how to use the SXGSEL routine Here follows two examples of how to use the SXGSEL facility. The first example uses the SH-banks, and it is assumed that one has generated muon-pairs with IGENER = 14. The selection criteria are that: e A photon with E > 5 GeV is present e The angle between the photon and any of the muons is > 10°. +KEEP> SXGSELBODY. REAL PP (3) >PMU1 (3) »PMU2 (3) > PGAM (3) LOGICAL FIRST FIRST = . TRUE. GAMENE = 8.8 % * Loop all! SH-banks LSH = LQ(LSE-4) 18 IF ( LSH .NE. @ ) THEN * Daughter IORUGH = @ IF ( LQ(LSH-1) .NE. @ ) THEN IDAUGH = NINT(Q(LO(LSH-1)49)) ENDIF * ST bank LST = LO(LSH-64) * No daughter => final particle IF ( LST.GT.8 .AND. IDAUGH.EQ.8 ) THEN PP(1) = Q(LSH+3) PP(2) = Q(LSH+4) PP(3) = Q(LSH+5) E = Q(LSH+6) * Particle is a gamma IF ( NINTCQ(LSH+1)) .£0. 21 ) THEN CALL UCOPY (PP»PGAN>3) — E.7- DELSIM Vers 3.2 IF ¢€ E .GT. GAMENE ) THEN GAMENE = E ENDIF ELSEIF (¢ ABS(NINT(Q(LSH4+1))) .£Q. 6 ) THEN * Particle is a muon IF (FIRST) THEN CALL UCOPY(PP,PMU1>3) FIRST = .FALSE. ELSE CALL UCOPY (PP, PMU2,3) ENDIF ENDIF ENDIF LSH = LQ(LSH) GO TO 18 ENDIF IF ( GAMENE .LT. 5.8) THEN IUSEIT = 8 ENDIF IF ( VDOTN(PGAM>PMU1>3) .GT. 8.9848 .OR. * VDOTN(PGAM>PMU2,3) .GT 8.9848 ) THEN IUSEIT = 8 ENDIF +next patchy card (other KEEP sequences) +USE;, P=SXGSEL. (other USE selections) +PAM. (DELSIM-pam) The second example uses the LUND common, and here it is assumed that one has generated qq-pairs. The selection criteria are that: e At least one Beauty-quark is present. e Among the particles after fragmentation, the total B quantum-number is either 2 or —2. +KEEP> SXGSELBODY. LOGICAL BINEV INTEGER B>BBAR B= 8 BBAR = 8 BINEV = .FALSE. DO 18 I = I5N IF € ABS(K(I>2)) .£0. S85 ) THEN BINEV = . TRUE. ENDIF 18 CONTINUE IF ( BINEV) THEN DO 11 IT = IsN IF ( K(I+2) .E£Q. 181 .OR. K(I>2) .EQ. 182 .OR. K(I>2) .£Q. 183 .OR. K(I,2) .EQ. 184 ) THEN B=B+l1 ENDIF IF ( K(I,2) .EQ. -181 .OR. K(I,2) .£Q. -182 .OR. K(I,2) .£Q. -183 .OR. K(I»2) .£Q. -184 ) THEN BBAR = BBAR + 1 ENDIF il CONTINUE IF (( B .EQ. 2 .AND. BBAR .EQ. 8) .OR. (B .EQ. @ .AND. BBAR .EQ. 2 )) THEN IUSEIT = 1 ELSE IUSEIT = 8 ENDIF ELSE IUSEIT = 8 ENDIF +next patchy card (other KEEP sequences) +USE> P=SXGSEL. (other USE selections) +PAN. (DELSIM-pam) —- E.8— DELSIM Vers 3.2 E.5 Control card file The following control card file (SIMRUN.TIT ) are using the standard DELSIM ZO generator with no radiative corrections and selects the muon decay of the Z°. It requests full detailed simulation in the detectors given on the MSIM control card. The DDML control card shows to which details the different modules have been loaded from the data base. This has been done in an earlier run and the fast loading of the pre —loaded data base is requested by the control card LDBZEB. LIST C-- Choose beam energy EBEAN 46 C-- Choose process IGENER 4 C-~ READ TEST EVENTS (ALREADY GENERATED EVENTS IN EXCHANGE MODE) FOR@11 C--IDTIN 3 C-- ZEBRA/TANAGRA INPUT/OUTPUT IN EXCHANGE DISK MODE IDTANA §=3 IDTOUT 3 C--- Select muon decay mode of the 28 (nue>e>uUsdsnums»muon>c»s»ntau> taus tsb) JPSEL 88§8@e8ele8g08886 C-- Maximum number of events to be generated NEVMAX 18 C-- Use simulation ISINUL 2 C-- Build SP and ST for the decays of short lived particles JSHORT TRUE C-~ Temporary stack requested JFLSTK = TRUE C-- Debug options IFEVDB 1 ILEVDB 18 ISNIDB «61 6 8 C-~ Print ISEEDS and ISEEDg every ITEST event ITEST 1 C-- Set minimum momentum for e and gamma PMINE 8.81 C-- Maxmimum number of spirals SPIRMX 25 C-- Set DD date and time DDDAT 898481. 128888. C-- Use old DDAPP288 SDVG records and ’288° data base SOVG TRUE C~- Suggested print level for diagnostics from data base package» DOAPP388 IDDPRT 1 C-- Optional print out all overlaid geometry» for DDAPP388 PRTOVE FALSE C-- Set default values for database level NLEV(1) = GEOM NLEV(2) = SENS DEV NLEV 2 8 C C-- detector levels and validity date for geometry & calibration data C-- "288" database : put LEVS = &. > no calibration data C-- LEVG = LEVG + 1888 » if SOVG wanted C-- "388" database : put LEVS = 1. >» Calibration data C-- LEVG = LEVG + 1888, if SDVG wanted C-- C-- detector date time Geometry Calibration C-- LEVG LEVS C C-- Select levels for loading the database DOML *BEA ” 898488. 128888. 2. 8. "VD ” 898481. 128888. 1882. 2. 71D ” 898481. 128888. 1882. 2. >TPC ? 890481. 126886. 1882. 2. *RIB ’ 898481. 128888. 2. 2. "0D ” 898481. 128888. 1882. 2. "HPC ’ 898481. 128888. 1. 8. *COl ” 898481. 128888. 2. 8. *TOF ” 898481. 128888. 2. 8. 7HAB ” 898481. 128888. 1882. 8. >MUB ” 888481. 128888. 2. 2. "FCA ? 898481. 128888. 1882. 2. "RIF ? 898481. 128888. 2. 2. "FCB ’ 898481. 128888. 1882. 2. "ENF ” 898481. 128888. 1882. 2. *HAF ° 898461. 128888. 1882. 8. -— E.9- DELSIM Vers 3.2 >MUF ” 898918. 128888. 1882. 2. >SAT ° 898481, 128888. 2. 2. *HOF ” §98481. 128688. 2 8. C-- END 388 DB MODULE SELECTIONS C-- Stop tracking in the following detectors MSTP BLK’ *°SCO ? C-- Do detailed simulation in the following detectors MSIM- = ?°VD ? °I0) *% °TPC * °OD * *FER ? *FCB ’ = *°TOF * *MUB *® °SAT ? "HPC ” ’EMF > °HAB * *HAF * *MUF ° "RIB ? °RIF ? c-- Save incoming tracks for detectors MTRS ’VD * °?ID * °TPC ? °OD ° >FER? "FCB ® *TOF * *MUB * *SAT ? "HPC ° ’EMF ° *HAB ’ °HAF * *MUF ° *RIB ’ *RIF ? C-~ Read in/Write out a copy of the loaded database WOBZEB FALSE on a ZEBRA structure LOBCEB TRUE END E.6 Example of control cards file for a run with Bhabha scattering C-- list control cards LIST C-- Switch MUSTRARL generator on IGENER 14 C--Electrons generated with Bhabha generator IBHABH 1 C-- Change minimum and maximum scattering angle (15-18 and 165~178) THEMIN 18 THEMAX 178 C-- Compute GSN constants to l-loop level (recommended for Bhabha) IZ1LOP 1 C-- Change mass of TOP quark for calculating GSH constants (38-42) AMNTOP 42. C-- The rest of the control cards can be as you Want (eg as in the C-~ previous example) E.7 Example of control cards file for a run with single particle generation In this example, 8 muons with different momenta are selected. LIST C-~~ Choose process IGENER 5 C-- Select the number of few particles NFEWPA 8 C-- Select single particle type SPNAMNE ’MU+ * ?MU- % °MU+ 7 °MU- > ?MUS > >MU- ? MU > MUL > C-- Select single particle momenta SPPMIN 1. 3. 5. 7. 9. 11. 15. 28. SPPMAX 1. 3. S. 7. 9. 11. 15. 28. C-- Select single particle theta SPTHMN 3. 3. 3. 3. 3. 3. 3. 3. SPTHMX 177, 177, 177, 177. 177. 177. 177. 177. C-- Select single particle phi SPPHMN 8. 8. 8. 8. 8. 8. 8. a. SPPHMX 368. 368. 368. 368. 368. 368. 368. 368. C-- Select single particle coordinates SPXMIN 8. 8. 8. 6. 8. 8. 8. &. SPXMAX 8. 8. 8. 8. 8. 8. 8. 8B. SPYMIN 8. 8. 8. 8. 8. B. B. B. — E.10 - DELSIM Vers 3.2 SPYMAX 8. 8. 8. ° @ SPZNIN 8. 8. 8. ® e SPZMAX 8. 8. &. Qone Qo Oo e Ooaae ooo E.8 Debug listing in the generation phase An example of a print output for debug level 1 of generation (in this case IGENER = | and 7? goes to tau taubar) is given here. First is the content of the different SH (history banks) given. Then is printed the tracks leaving the primary interaction vertex (in this case the two taus). Since the short lived particle verticies have been lifted (ISHORT = TRUE ) they are also printed here. The incoming track to the vertex has negative track number. LIST OF SH-BANK CONTENTS TINDX NANE CHRG PAR DAU mn od wn TYPE MASS PX PY TAU~ -1. DECAY 1.784 43. 881 13.577 -589 - 888 PT-~ -1. BR FINAL 8.148 . 169 3.811 . 999 -981 WNHe PI8@ WON 8.135 26. be 193 9.617 -918 - 855 NUTA be © © FINAL 8.888 -639 2.149 -672 - 964 TAU+ © DECAY 1.784 -43. 881 ~15.577 -589 - 888 OME E+ U1 FINAL 8.881 -7. 231 ~2.869 - 887 NUE OT FINAL 8.888 ~14. 573 -5.393 - 369 - 569 NUTB UT FINAL 8.888 21. 138 -7.315 328 -944 GAMM - FINAL 8.888 is. 597 5.797 735 -729 ~~ BOON GAMM SaOnnonrr GG RDQVDDAMNA QVODonaaorwwn FINAL 8.888 18. 596 3.828 - 183 ~326 Sum for final state particles: 92.888 . 888 8.888 . 888 Final state particles at 8.888 8.8 88 8.888 NUMB PART Pp PY P2 1 TAU- 1.784 43.881 15 -577 ~4,589 46. 888 4 TRAU+ 1.784 -43.881 ~15 ~977 4.589 46. 888 Total 9 2.888 8.888 8.888 8.888 $2. 888 Final state particles at 8.196 8.8 71 -8 -821 NUMB PART M PX PY P2 TAU~ 1.784 -43.881 -15 -577 4.589 46. 888 Wr NUTA 8. 888 7.639 2 . 148 ~8.672 - 964 PI~ 8.148 3.169 3 -81i ~8.999 981 GAMNM 8.888 15.597 3 . 797 16. 729 OMN GAMM 8.888 18.596 3 - 828 -1.183 il. 326 Total 1.784 43.881 1S. 577 -4.589 46. 888 Final state particles at -8.863 -8.8 23 8.887 NUMB PART M PX PY -4 TAU+ 1.784 43.881 1s ~577 -4.589 46. 888 7 NUTB 8.888 -21.198 -7 ~315 2.328 22. 544 6 NUE 8.888 -14.573 -5 - 393 8.969 is. 569 5 E+ 8.881 -7.231 -2 . 869 1.388 7. 887 Total 1.784 ~43.881 -15 -577 4.589 46. 888 Event accepted by SXGSEL after 1 tries — E.ll - DELSIM Vers 3.2 E.9 Debug listing of the simulation history. This output is generated when choosin g the control card IFPREV= ]. Vertices 2, show the incoming track parameters 5, 8 and 9, at the e nd point (note the negative track lenght). Event é: temporary storage called for 6 tracks Maximal use was 2 vertices and 2 tracks Ver tex 8 Type = Prim xeyrz = 8.8 8.8 8.8 Det = BEA Track Type Mass Time (ns) ch Px Pz 1 Py E Length Detec pe Deca TAU- - 43.881 15.577 ~4, 589 4 46. 888 8.2891 BEA LY Deca TAU+ + -43.881 -15.577 4. 583 46.888 8.8678 BEA Ver tex 1 Type = Deca XYZ = 8. 2 8.1 6.8 Det = BEA Track Type Mass Time (ns) ch Px Py Pz E Length Detec be Prim TAU- - -43.881 © -15.577 589 46.888 -8.2891 BEA J G) Leavy NUTA 8 7.639 -8. 672 7.964 8. 8888 HInt PI- - 9.169 -8. 999 $.981 349.4622 HAB ON) Show GAMM 8 15.597 -1. 735 16.729 289.9438 HPC © OOhe Show GANM 8 18.596 -1. 183 11.326 289.7636 HPC Ver tex 4 Type = Deca x»yz 8. 8.8 Det = BEA Track Type Mass Time (ns) ch Px Pz E Length Detec Prim TAU+ & + 43.881 - 989 ~1 46.888 -8.8678 BEA Leav NUTB 8 +~21.198 ~328 ~1 22.544 8.8888 Leav NUE 8 -14.573 - 963 15.569 8. 8888 ON Show E+ + -7.231 - 388 7.887 211.4873 HPC Ver tex 2 Type = HInt) xsyoz tt nm G ~~ 153. -34.5 Det = HAB Track Type Mass Time (ns) ll. ch Px Po E Length Detec 1 Deca PI- - ~8.857 -4.497 546 3.244 -349.4622 BEA Ver tex 8 Type = Show xyz 72. ~21.8 Det = HPC Track Type Mass Time (ns) ch Px Ps E Length Detec 8 1 Deca GAMM 8 ~15.597 -5.797 £735 16.729 -289.9438 BEA Ver tex 3 Type = Show XYZ 78.8 -21.9 Det = HPC Track Type Mass Time (ns) ch Px Po E Length Detec 9 1 Deca GAMM 8 -18.596 183 11.326 -289.7636 BEA Ver tex S Type = Show xyz .3 ~67. 34.8 Det = HPC Track Type Mass Time (ns) ch Px Pz E Length Detec 5 4 Deca E+ + 7.381 -l. 254 7.785 -211.4873 BEA E.10 Debug listing of the Zebra structure This is the ZEBRA structure which is reported when choosing IZEBDB = 1. DZSURV --~ DATA STRUCTURE 698177 ST= /SXCZEB/ LSTART= NWCUM NN WBK NBK IDENTIFIER(S) 18 18 18 1 TO Pp 58 32 32 1 -1 RAW 73 23 23 1 6 RVD 171 98 98 1 -5 RAND 223 $2 32 2 -7 RID TDL 248 17 17 1 -2 IORL 3516 3276 1783 6 -5 IORJ IDRA IORC IDLJ IOLA IOLC 3 §98283/1222 PAGE 3566 58 25 2 -8 RTPS RTP1 7488 = 3914 «1378 4 -5 DATS TRAB DAT TRAIL 7583 23 23 1 -9 RRIB 7764 261 8261 1 -5 RAND 7787 23 23 1 -18 ROD 7854 67 67 1 -5 RAWD 7889 35 35 1 -1l RHPC 7928 31 31 1 -2 HT12 8778 858 858 1 -5 HPRD 8854 76 76 1 -6 HMCI 8877 23 23 1 RTOF 9271 394 394 1 -5 RAWD 9294 23 23 1 RHAC 9322 28 28 1 -5 RAWD 9347 25 25 1 -14 RMUB — E.12 - DELSIM Vers 3.2 3363 16 16 1 -2 T1T2 9832 469 469 1 ~5 RAWD 9862 38 38 1 ~7 SINR 9885 23 23 1 -~15 RFCA 9974 89 45 2 -S RAWD LABL 9997 23 23 1 -17 RSAT 18845 48 48 1 -~2 T1T2 18347 382 382 1 -S RAWD 18378 23 23 1 -~18 RFCB 18448 78 35 2 -5 FCB FCBL 18488 48 26 2 ~l1 BRAW BLAB 18828 48 26 2 -2 BRAW BLAB 18568 48 26 2 -~3 BRAWN BLAB 18688 48 26 2 -4 BRAW BLAB 18648 48 26 2 ~S BRAW BLAB 18688 48 26 2 -6 BRAW BLAB 18728 48 26 2 ~7 BRAWN BLAB 18768 48 26 7 ~8 BRAW BLAB 18888 48 26 2 -3 BRAWN BLAB 18848 48 26 2 ~18 BRAW BLAB 18888 48 26 2 -11 BRAW BLAB 18928 48 26 2 ~12 BRAWN BLAB 18968 48 26 2 -~13 BRAW BLAB 11888 48 26 2 ~14 BRAW BLAB 11848 48 26 2 -15 BRAW BLAB 11888 48 2 2 -16 BRAW BLAB 11128 48 26 2 -17 BRAW BLAB 11168 48 2 2 ~18 BRAW BLAB 11288 48 26 2 ~19 BRAWN BLAB 11248 48 26 2 -~28 BRAWN BLAB 4 898283/1222 PAGE 11288 48 26 2 -21 BRAW BLAB 11328 48 26 2 -~22 BRAWN BLAB 11368 48 2 2 -~23 BRAW BLAB 11468 48 26 2 -~24 BRAN BLAB 11424 24 24 1 ~19 REMF 11435 ll li 1 -1 EERR 12841 686 686 1 -2 ET12 12864 23 23 1 -5 ERND 12877 13 13 1 ~6 ENCI 12184 27 27 1 -5 SE 12122 18 18 1 -1 SP 12178 S6 2 2 -1 ST 12286 188 18 6 -2 SP 12658 364 28 13 ~1 ST 13238 S88 28 829 -1 SX 13255 25 25 1 -3 SI 13585 25 25 18 -4 SH 13537 32 32 1 -6 TRG 13558 13 13 1 ~13 TRGH 13572 22 22 1 -2 TRO2 13683 31 31 1 -7 SIMP 13723 128 38 4 -6 RTRA 13823 188 25 4 ~7 RTRA 13873 58 25 2 ~8 RTRA 13923 $8 25 2 ~9 RTRA 14888 165 98 4 ~18 RTRA 14288 112 28 4 -11 RTRA 14225 25 25 1 -12 RTRA 14258 25 25 1 -13 RTRA DZSURV --~ The structure supported by bank TOP at 698177 in store /SXCZEB/ occupies 14258 words in 186 banks — E.13 - DELSIM Vers 3.2 Reference and index tables DELPHI Technical proposal, CERN/LEPC 83-3, LEPC/P2; DELPHI 83— 66/1. DELPHI event generation and detector simulation: Reference manual, DELPHI 87—98 PROG — 100. PATCHY Manual CERN Library CERN Pool programs W5035/W5045/W5046/ W3047/W5048 log writeup April 1987. A.Ali, B. van Eijk and I. ten Have, Nucl. Phys. B292(1987) 1; B. van Eyjk, PhD thesis, Uni- versity of Amsterdam (1987), unpublished. Detector Description Application Package: User Manual for version 3.00, Yu.Belokopytov et al., DELPHI 88— 87 PROG— 121. Detector module reference writeups, to be published. TANAGRA Track Analysis and Graphics Package — User's Guide, D.Bertrand, L.Pape, DELPHI 87-95 PROG— 98. FASTSIM Simulation for DELPHI , J.Cuevas et al., DELPHI 87-27 Prog—72 Rev. 10. FFREAD— CERN program library. 11. Detector Dependent Graphics Implementation Guide Lines, D.Bertrand et al., DELPHI 89—9 PROG— 128 12. F.A.Berends,R.Kleiss and S.Jadach, Comm. Comp. Phys. 29 (1983) 185. 13. P.S.Iversen, DELPHI 85—31 PROG— 23. 14. DELPHI Event Data Layout: Online and Offline Formats Ph.Charpentier et al., DELPHI 88-64 PROG— 115 DAS— 88. 15. H.J.Hilke, DELPHI 84—40 GEN-— 10 DELSIM Vers 3.2 DELSIM control cards index AMHIGS ... 3.3, A.4 IRUN ... 5.4, A.3 AMTOP ... 3.3, 3.7, A.4 ISEED ... 2.8 AMZ ... 3.3, A.4 ISEEDG ... 2.8, A.2 ISEEDS ... 2.8, A.2 BDOS ... A.5 ISIMUL ... A.4 BSOS ... A.5 ISWIDB ... 2.6, A.1 ITEST ... A.2 CONMZ ... A.4 ITIN ... A.l CTHIGH ... A.5 ITMULS ... A.3 CTLOW ... A.5 ITOUT ... 2.9, Al ITPLT ... A.l DDDAT ... 5.4, A.3 IZ1LOP ... A.4 DDML ... 5.4 DEBEAM ... A.4 JANNIH ... A.3 DPMAX ... A.2 JBREMS ... A.3 DPREC ... 4.4, A.2 JCOMPT ... A.3 DTMAX ... A.2 JDECAY ... A.3 JDRAYS ... A.3 EBEANM ... A.4 JFAST ... A.l EUROEFR ... 3.2, A.5 JFLGLU ... 2.10, A.2 Examples control card file ... E.9 JFLGSH ... 3.6, 6.2, A.2 Examples debug printing ... E.11—E.12 JFLPRM ... A.2, C.1 JGLU ... A.4 FRACLE ... 4.4, A.2 JHAINT ... A.3 JPAIRS ... A.3 IBEAM ... A.4 JPHOTO ... A.3 IDB ... 2.6, A.4 JPSEL ... 2.5, 3.1, A.5 IDDFZI ... A.3 JPSELH ... 3.1, A.5 IDDFZO ... A.3 JPSELZ ... 3.1, A.5 IDDOVE ... A.3 JPSLHM ... A.5 IDDVPR ... A.3 JPSLHP ... A.5 IDDVTY ... A.3 JSEL ... A.5 IDLUIN ... 3.8, A.l JSHORT ... 3.6, 6.4, A.4 IDLUUT ... 2.9, A.l JTETS ... 2.8, A. IDST ... 4.4, A.2 IDTANA ... A.l LABO ... A.1 IDTIN ... 2.10, A.l LDBZEB ... 5.6, A.3 IDTOUT ... 2.9, A.1 LEUDAT ... A.1, A.5 IEV1 ... 2.10, A.4 LEUTIT ... A.1, A.5 IFEVDB ... 2.6, A.1 LOUTAN ... 2.9, A.l IFIXEN ... A.5 LUNDBZ ... 5.6, A.1 IGENER ... 3.1, A.4 ILEVDB ... 2.6 MDB1 ... 2.7, A.l IPRNT ... A.l MDB2... 2.7, A.1 IREAD ... A.] MDB3.... 2.7, A.l -—-2?- DELSIM Vers 3.2 MODOSC ... A.5 XMH1 ... A.5 MSIM ... 5.1, A.3 XNFAMS ... A.4 MST ... A.4 XS ... A.5 MSTE ... A.4 XYZW ... 3.3, A.4 MSTP ... 4.4, A.3 MTRA ... 5.1 MTRS ... A.3 NCONMX ... A.3 NEVMAX ... A.4 NFEWPA ... A.6 NLEV ... 5.4, A.3 NMEDM«X .... A.3 NSDECY ... A.4 PAR ... A.4 PARE ... A.4 PMAS ... A.4 PMIN ... A.2 PMINE ... A.2 PMINH ... A.2 RATMIN ... A.2 SPIRMX ... A.2 SPNAME ... A.6 SPPHMN ... A.6 SPPHMxX ... A.6 SPPMAX ... A.6 SPPMIN ... A.6 SPTHMN ... A.6 SPTHMX ... A.6 SPXMAX ... A.6 SPXMIN ... A.6 SPYMAX ... A.6 SPYMIN ... A.6 SPZMAX ... A.6 SPZMIN ... A.6 SSQT ... 3.3, A.4 STEP ... A.2 STEPM ... A.2 STEPMD ... 4.4, A.2 SXPBLEK ... 3.6 TLMAX ... A.2 TRKLMxX ... A.2 VTAU ... 3.6, A.4 WDBZEB .... 5.6, A.3 XD ... A.5 XLAMC ... A.5 XLMIN ... A.2 DELSIM Vers 3.2 DELSIM subroutine index DEFCAL ... 5.4 SxSUM ... 5.1 DEFGEO ... 5.4 SXTRAF ... 4.2 DFMODR ... 5.4 SXUEND ... 3.8 SXUFFER ... 3.8 LUEEVT ... 3.2—3.3 SXUINT ... 3.4, 3.8 SXUSGE ... 3.2, 3.4, MODBLO .... 6.4 3.8 SXWRLU ... 2.9 SXZH ... 3.3 SXBEAM ... 3.3 SXZZ ... 3.3 SXBEG ... 5.1 SXBKGZ ... 3.3 UPCON ... 7.] SXCTRK ... 4.2 UPNAM ... 3.6, 7.1 SXDATA ... 2.5—2.6 USHIST ... 2.8 SXDCOM ... 7.3 SXDDAP ... 4.2 SXDETX ... 4.2 SXEEGG ... 3.3 SXEJET ... 3.4 SXEND ... 5.1 SXFELT ... 4.2 SXGEIN ... 3.3 SXGENE ... 3.4 SXGLUN ... 3.4 SXGSEC ... 4.2 SXGSEL ... E.7 SXGSUS ... 3.4 SXHH ... 3.3 SXIMAT ... 3.3 SXINI ... 5.1 SALULB ... 3.4, 6.2 SXLULP ... 3.4 SXLUND ... 3.3 SXLUST ... 3.4 SXLUZE ... 3.4 SXMEDI ... 7.3 SXPSEC ... 4.2 SXRDLU ... 2.10, 3.8 SXREAD ... 2.5 SXSAVE ... 2.7 SxSIM ... 5.1 SXSIMU ... 4.2—4.3 SXSING ... 3.3 SXSLA ... 3.3 SXSQA ... 3.3 SXSQG ... 3.3 DELSIM Vers 3.2 General DELSIM index Activating module simulation ... 5.1 Fast loading of data base ... 5.6 Fast simulation ... 2.1, B° - B° Oscilations 2.10, A.l ... 3.7 FFREAD ... 2.5 B°—B?® ... A.5 Final state particles ... 6.3 Beam Energy ... A.4 Fragmentation models ... 3.2 Beam spot width ... 3.3, A.4 Bhabha scattering ... 3.2 Generators ... 3.1 Building up the Lund common from ZEBRA Gluon generation ... 3.4 input ... 2.10 Graphics output ... 2.8, A.1 Change particle lifetimes ... 3.6 Hadronic interactions ... 4.1 Change particle masses ... 3.7 HBOOK ... 2.4 Change TOP quark mass ... 3.7 HBOOK4 ... 2.4 CONTROL CARDS ... 2.5 Higgs particle generation ... 3.3 Control cards for EUROJET ... A.5 Histogram ... 2.4, 2.8 Control cards for LUND ... A.4 History bank ... B.5 Coordinate system ... 7.1 History of fragmentation ... 6.2 Database ... 5.4 Input ZEBRA structure ... 2.10 DDAPP ... 5.4 Input/ouput ... 2.6 Debug control ... A.1 Input/output ... 2.9, A.1 Debug example ... E.11—E.12 IRUN. ... 5.4 Debugging facilities ... 2.6 Decay constants ... D.1 JFLOUT ... 7.3 Detector components ... 7.3 JPSEL ... 3.1 Detector description ... 4.1 Detector simulation ... 4.1—4.2, 5.1 LINKPROC on VAX VMS ... E.2 Distance prediction ... 4.4 Loading database ... A.3 Dummy routines ... 5.2 Loading detector description ... 5.4 LUJETS ... 3.2 EGS ... 4.1 LUND common input ... 3.8 Electromagnetic interactions ... 4.1 End of run records ... 2.10 Magnetic field ... 4.2 EURODEC TITLE file ... 3.2 Material constants ... 7.3 EUROJET fragmentation ... 3.2 Module dependent parameters ... 5.3 Event generation ... A.4 Module simulation ... 5.] Event selection ... 3.5 Event simulation ... A.4 Ouput ZEBRA banks ... 2.9 Examples ... E.2, E.7, E.10 Output Lund common ... 2.9 Bhabha scattering control cards ... E.10 Output unit for Lund data ... 2.9 Example of use of SXGSEL routine ... E.7 Output unit for TANAGRA ... 2.9 Examples create a EXE file on VAX ... E.2 Output unit for ZEBRA ... 2.9 Single particle control cards ... E.10 Examples of runs ... 2.1 PA vector ... 6.1 External generator ... 3.2, 3.8 Particle code ... 7.1—7.2 —~5- DELSIM Vers 3.2 Particle conventions ... 7.1 Units ... 7.1 Particle decay constants ... D.1 Use of SXGSEL ... E.7 Particle description ... 6.1 User control cards ... 2.6, E.4 Particle lifetimes ... 3.6 User generator ... 3.8 Physics processors ... 4.1 Pilot record ... 2.10 Vertex data bank ... B.3 Plots ... 2.8, E.4 Vertex labels ... 7.2 PMB bank ... B.2 VM example ... E.4 Point of entrance of detector modules bank ... B.4 Weak angle (sin?O) ... 3.3 Quark fragmentation models ... 3.2 ZEBRA data structure ... 6.2 Quark hadronization ... 3.4 ZEBRA pilot record ... 2.10 Radiative corrections ... 3.2 Random number generator ... 2.8 Random numbers ... A.2 RAW bank ... 6.4, B.1 RAW data header bank ... B.1 Raw data module header bank ... B.2 RAWH bank ... 6.4 Read in Lund format ... 2.10 Reduce the size of EXE files on VMS ... E.2 Run deck ... 2.2, E.2 Run deck for VAX ... E.2 Run number ... 5.4 SE bank ... 6.2, B.2 Secondary processes ... 4.1, A.3 Select event on input file ... 2.10 Selecting generated events ... E.7 SH bank ... 6.2, B.5 Short decay ... A.4 Short lived particles ... 3.6, 6.4 SI bank ... 6.2, B.4 Single particle control cards ... E.10 Single particle generator ... 3.3 Single particles control cards ... A.6 SP bank ... 6.3, B.3 ST bank ... 6.3, B.3 Start of run records ... 2.10 Stop tracking ... 4.4 SX bank ... B.4 Tanagra output ... A.1 TATINA ... 4.1 Tau polarization ... 3.6 Temporary track bank stack ... 6.4 TOP bank ... 6.2, B.1 Track bank ... B.3 Track following ... 4.2 Track labels ... 7.2 Tracking parameters ... 4.2, A.2