source: branches/AddingGoogleTestEnvironment/mmc/MTriggerDefine.h@ 19779

Last change on this file since 19779 was 7880, checked in by tbretz, 18 years ago
*** empty log message ***
File size: 3.7 KB
Line 
1#ifndef MARS_MTriggerDefine
2#define MARS_MTriggerDefine
3//
4//
5// In this file are the fundamental definitions for the class MCTrigger
6//
7// Number of pixels in the trigger region (used by camera simulation,
8// see camera.cxx.
9//
10#define TRIGGER_PIXELS_1 397
11#define TRIGGER_PIXELS_2 397
12#define TRIGGER_PIXELS_3 1657
13#define TRIGGER_PIXELS_4 547 // For MGeomCamMagic1183, PRELIMINARY!
14#define TRIGGER_PIXELS_5 397
15#define TRIGGER_PIXELS_6 1657
16#define TRIGGER_PIXELS_8 126
17#define TRIGGER_PIXELS_9 126
18//
19// This is the number of Pixels contributing to the TRIGGER logic
20// for each of the already implemented geometries.
21// All Pixels-Id above that value don't do an trigger stuff.
22// Actually, not all of them are involved in TRIGGER logic, only the
23// ones of them that are also in some TRIGGER_CELL
24// (MagicSoft/Simulation/Detector/include-MTrigger/TABLE_PIXELS_IN_CELLS)
25//
26#define TOTAL_TRIGGER_TIME 160
27//
28// This values defines the total range in that we try to find
29// a trigger.
30//
31#define LEVEL1_DEAD_TIME 50
32//
33// Dead time of the detector after one first level trigger happens.
34//
35#define LEVEL2_DEAD_TIME 300
36//
37// Dead time of the detector after second level trigger fires
38//
39#define TRIG_SLICES_PER_NSEC 4
40//
41// Each nano second is divided into the number of this values slices.
42// So you can get the total number of timeslices for one Pixel by
43// ( TOTAL_TRIGGER_TIME * SLICES_PER_NSEC ).
44// In the current settings this are 1000 slices
45//
46#define TRIGGER_TIME_SLICES (TOTAL_TRIGGER_TIME*TRIG_SLICES_PER_NSEC)
47//
48//
49//
50//
51// ------>>> SETTINGS for the RESPONSE FUNCTION
52//
53#define RESPONSE_SLICES_TRIG 40
54//
55// This is the dimension of the array containing the standard response Signal
56// for 1 Photoelectron, as seen at the input of the discriminators (for the
57// trigger simulation). Each bin corresponds to 1./TRIG_SLICES_PER_NSEC nanoseconds,
58// so by default it is 0.25 ns and hence the total range is 10 ns. This should be
59// enough for any reasonable single photoelectron response (should be much narrower
60// than 10 ns!)
61//
62
63// The Response function
64// These values are discussed with Eckart. We start from this point.
65//
66#define RESPONSE_FWHM 2.
67
68#define RESPONSE_AMPLITUDE 1.
69//
70// This are the Standard values of the response function for
71// 1 photo electron. ( 1 means 1 mV per photoelectron )
72//
73//
74// -------->>> SETTINGS for the DISKRIMINATORS
75//
76//
77#define CHANNEL_THRESHOLD 2.5
78//
79// This is the diskriminator threshold for each individual channel
80// First we set the value to 2 unit of the RESPONSE_AMPLITUDE
81//
82#define TRIGGER_GATE 3.
83//
84// Here we set the width of the digital signal we get if the signal
85// passes the diskriminator
86//
87//
88#define TRIGGER_OVERLAPING 0.25
89//
90// Here we set the required overlaping time among pixels
91// to be in coincidence.
92//
93//
94// --------->>>> SETTINGS for the TRIGGER logic
95//
96//
97#define TRIGGER_CELLS 19
98//
99// Number of trigger cells that cover the trigger zone
100//
101#define TRIGGER_MULTI 4.
102//
103// We get a Level Zero Trigger, if we have a least TRIGGER_MULTI
104// channels with a diskrimiator signal at the same time
105//
106#define TRIGGER_GEOM 0
107//
108// This defines the geometry required for a trigger. There exists
109// different meaning for this behaviour:
110// 0 means a pixel with trigger_multi-1 neighbours
111// 1 means trigger_multi neighbours
112// 2 means trigger_multi closed neighbours
113//
114#endif
Note: See TracBrowser for help on using the repository browser.