source: trunk/MagicSoft/Simulation/Detector/include-MTrigger/MTriggerDefine.h@ 390

Last change on this file since 390 was 373, checked in by harald, 25 years ago
This is the Version of MTrigger Class from the 10th of March 2000. Some work was done by Oscar Blanch and Harald Kornmayer.
File size: 2.3 KB
Line 
1//
2//
3// In this file are the fundamental definitions for the class MCTrigger
4//
5//
6#define TRIGGER_PIXELS 271
7//
8// This is the number of Pixels contributing to the TRIGGER logic
9// All Pixels-Id above that value don't do an trigger stuff.
10//
11//
12#define TOTAL_TRIGGER_TIME 160
13//
14// This values defines the total range in that we try to find
15// a trigger.
16//
17#define SLICES_PER_NSEC 4
18//
19// Each nano second is divided into the number of this values slices.
20// So you can get the total number of timeslices for one Pixel by
21// ( TOTAL_TRIGGER_TIME * SLICES_PER_NSEC ).
22// In the current settings this are 1000 slices
23//
24#define TRIGGER_TIME_SLICES (TOTAL_TRIGGER_TIME*SLICES_PER_NSEC)
25//
26//
27//
28//
29// ------>>> SETTINGS for the RESPONSE FUNCTION
30//
31#define RESPONSE_SLICES 40
32//
33// This is for the standard response Signal to 1 Photoelectron
34// that leaves the Photocathode
35// The whole Timescale for the signal is 10 nsec
36//
37// The Response function
38//
39// These values are discussed with Eckart. We start from this point.
40//
41#define RESPONSE_FWHM 2.
42
43#define RESPONSE_AMPLITUDE 1.
44//
45// This are the Standard values of the response function for
46// 1 photo electron. ( 1 means 1 mV per phote electron )
47//
48//
49// -------->>> SETTINGS for the DISKRIMINATORS
50//
51//
52#define CHANNEL_THRESHOLD 2.5
53//
54// This is the diskriminator threshold for each individual channel
55// First we set the value to 2 unit of the RESPONSE_AMPLITUDE
56//
57#define TRIGGER_GATE 3.
58//
59// Here we set the width of the digital signal we get if the signal
60// passes the diskriminator
61//
62//
63// --------->>>> SETTINGS for the TRIGGER logic
64//
65//
66#define TRIGGER_MULTI 4.
67//
68// We get a Level Zero Trigger, if we have a least TRIGGER_MULTI
69// channels with a diskrimiator signal at the same time
70//
71#define TRIGGER_GEOM 0
72//
73// This defines the geometry required for a trigger. There exists
74// different meaning for this behaviour:
75// 0 means a pixel with trigger_multi-1 neighbours
76// 1 means trigger_multi neighbours
77// 2 means trigger_multi closed neighbours
78//
Note: See TracBrowser for help on using the repository browser.