README for Ecal Pretrigger Simulation
README
This text gives you a short introduction to the usage of a simple
simulation of the ECAL pretrigger within ARTE. For further questions,
comments... mail to me:
mino@mail.desy.de
Usage:
Add the following line into the file uskuip.cdf:
#include "ECPT.inc"
Moreover you have to include
#include "care/EcalPretrigger.h"
in each file where you use this simulation.
Initialisation:
For initialisation there are some commands you can put in your kumac-file.
Each command is called by the identifier 'ECPT' followed by a string of
four characters specifying the command and a list of numerical parameters.
Now the commands in detail:
ECPT 'init' magnetOn cut geoMode
General initialisation:
magnetOn:
0 -> magnet off, use pt-cut
1 -> magnet on, use Ktrig-cut
cut:
value of Ktrig- or pt-cut, depending of magnet on/off
geoMode:
0 -> full geometrical acceptance
1 -> use geometrical acceptance given by the definition of
rectangular regions of the ECAL (see command 'rect')
2 -> use geometrical acceptance given by the frondend driver
identification numbers (fdid) (see command 'fdid')
ECPT 'rect' x1 y1 x2 y2
Add a rectangular region of the ECAL (given in cm) to a list internally
managed by the simulation. If you use the geoMode 1 (see command 'init')
the simulation checks for each hit in ARTE table HITC if it lies in one
of the defined rectangluar regions (you can add a arbitrary number of
regions).
ECPT 'fdid' id
Add a frondend driver identification number to a list internally managed
by the simulation. If you use geMode 2 (see command 'init') the simulation
checks for each hit in ARTE table HITC if corresponds to one of the
specified frondend drivers. If you want to know about which frondend
drivers were installed in which run, please ask Mauro Villa. A typical
setup for the time of March and April '99 is given by the following
numbers:
16 17 18 19 20 21 22 23 32 33 34 35 58 59 60 61 70 71 72 73 84 85
(no guarantee!)
Interactive commands:
The following commands may help you during an interactive ARTE session:
ECPT 'tows'
The HITC table is read out and towers exceeding the given cut are
searched. The number of triggering towers is printed.
ECPT 'clus'
The HITC table is read out and clusters exceeding the given cut are
searched. The number of triggering clusters is printed.
ECPT 'dump' ecalRegion
After using the commands 'tows' or 'clus', you can have a look on the
occupancy of the ECAL. Specify the ECAL region - inner, middle or outer -
by the parameter ecalRegion using the values 0, 1 or 2. You get a ASCII
plot where a '+' signifies a hit and a '#' signifies a tower/cluster
exceeding the given cut.
Direct access to the simulation:
Beside the kumac commands you call direct call some functions of the
simulation. You may use these functions in you analysis software after
including the file 'EcalPretrigger.h'.
int EcalPretrigger::processTowers()
This function corresponds the the kumac command ECPT 'tows' and returns
the number of triggered towers after looking up the HITC table. A tower
triggers if it exceeds the given pt- or Ktrig-cut.
int EcalPretrigger::processClusters()
This function corresponds the the kumac command ECPT 'clus' and returns
the number of triggered clusters after looking up the HITC table. A
cluster trigger is defined by a tower exceeding half of the cut-value and
the eight neighbor towers exceeding in sum with the viewed tower the full
cut-value.