]>
Commit | Line | Data |
---|---|---|
b6e1e92d | 1 | $Id$ |
2 | ||
3 | ||
4 | The mapping package | |
5 | ==================== | |
6 | ||
7 | See detailed description in ALICE-INT-2003-025. | |
8 | ||
9 | Test macros | |
10 | ============ | |
11 | cd ../mapping/macro | |
12 | root | |
13 | root [0] .x testMacroName.C | |
14 | - see available macros below | |
15 | ||
16 | A set of test macros be run at once by test_suite.pl scripts: | |
17 | test_suite.pl - run all test macros and compare results with | |
18 | the reference output | |
19 | test_suite_ref.pl - generates reference output | |
20 | !! this script will overwrite the refence output | |
21 | provided with the source; | |
22 | it should be used only by developers | |
23 | ||
24 | Macros included in the test suite: | |
25 | testReadSector.C | |
26 | testReadMotifType.C | |
27 | testGraphics.C | |
28 | testSectorFind.C | |
29 | testPlaneFind.C | |
30 | testPrintLimits.C | |
31 | testExistingPads.C | |
32 | testPadDimensions.C | |
33 | testSectorPadIterators.C | |
34 | testMotifTypeIterators.C | |
35 | testNeighboursPadIterator.C | |
36 | testAnyPadIterators.C | |
37 | testPadsUp.C | |
38 | testPlaneAreaIterator.C | |
39 | ||
40 | Other macros (not included in the test suite): | |
41 | testAllIndices.C | |
42 | testUpdateGlobalIndices.C | |
43 | ||
44 | ||
45 | Data files format | |
5149305f | 46 | ================= |
b6e1e92d | 47 | |
48 | zones.dat: | |
49 | ------------- | |
50 | Describes layout of zones, rows, row segments, subzones, motifs | |
51 | ||
52 | SECTOR_DATA | |
53 | number of zones | |
54 | number of rows | |
55 | direction of constant pad size (X or Y) | |
14b7b896 | 56 | offset in X direction |
57 | offset in Y direction | |
b6e1e92d | 58 | |
59 | ZONE | |
60 | number of zone | |
61 | half legth of pad size in x | |
62 | half legth of pad size in y | |
63 | ||
64 | SUBZONE | |
65 | motif id | |
66 | motif type_id | |
67 | ||
68 | ROW_SEGMENT | |
69 | x offset (in number of pads) | |
70 | y offset (in number of pads) | |
71 | row number | |
72 | nof motifs | |
73 | first motif position Id | |
74 | step to the next motif position Id (+1 or -1) | |
75 | ||
76 | zones_special.dat: | |
77 | ------------------ | |
78 | Describes layout of special row segments (with irregular motifs) | |
79 | ||
80 | SECTOR_SPECIAL_DATA | |
81 | ||
82 | MOTIF | |
83 | zone id | |
84 | motif id | |
85 | motif type_id | |
86 | ||
87 | ROW | |
88 | row number | |
89 | ||
90 | PAD_ROWS | |
91 | number of these pad rows in row | |
92 | ||
93 | PAD_ROW_SEGMENT | |
94 | mumber of pads in the rows segment | |
95 | motif id | |
96 | motif position id | |
97 | ||
98 | motifX.dat | |
99 | ---------- | |
100 | Describes characteristics of the motif type X | |
101 | ||
102 | In lines: | |
103 | Berg number | |
104 | Kapton number | |
105 | Pad number | |
106 | Gassi number | |
107 | ||
108 | motifSpecialX.dat | |
109 | ------------------ | |
110 | Describes characteristics of the special motif with motif Id X; | |
111 | the special motif caontains pads of different size | |
112 | ||
113 | In lines: | |
114 | pad index i (in x) | |
115 | pad index j (in y) | |
116 | half legth of pad size in x | |
117 | half legth of pad size in y | |
118 | ||
119 | padPosX.dat | |
120 | ----------- | |
121 | Maps pad numbers used in the motifX.dat files to | |
122 | the local pad indices (i,j) | |
123 | ||
124 | In lines: | |
125 | Pad number | |
126 | pad index i (in x) | |
127 | pad index j (in y) | |
128 | ||
5149305f | 129 | |
130 | *.pcb files | |
131 | ============ | |
132 | ||
133 | Lines starting with # are comments. | |
134 | ||
973884d7 | 135 | SIZES PadSizeX PadSizeY SizeX SizeY (cm) |
5149305f | 136 | |
137 | MOTIF motifType ix iy | |
138 | MOTIF motifType ix iy | |
139 | ... | |
140 | ||
141 | where ix, iy are the local coordinates (in pad unit) of the | |
142 | lower-left corner of the motif (0,0 is the lower-left corner | |
143 | of the PCB). | |
144 | ||
145 | PCB *MUST* be described in a rotating way, starting lower-left and | |
146 | then counter-clockwise, otherwise the manu-to-motif association | |
147 | (fixed in the slat definition files) will be wrong. | |
148 | ||
149 | Note that for "full" PCBs, the SizeX and SizeY are redundant as they could be | |
150 | computed from the motif alone (but that serves as a cross-check that the motif | |
151 | pattern given is ok). That's not the case for short or rounded PCB though. | |
152 | ||
153 | *.slat files | |
154 | ============= | |
155 | ||
156 | A slat is defined by the list of its PCB, described starting | |
157 | from the beam and going outward. | |
158 | ||
159 | One PCB per line, preceded by the keyword PCB | |
160 | Other lines not matching this syntax are ignored. | |
161 | After the PCB is the list of manu ids for this PCB. | |
162 | ||
163 | Example : | |
164 | ||
165 | PCB X 1-3;24-20;42;44;53 | |
166 | PCB X 1-14 | |
167 | PCB Y 100-90 | |
168 | PCB Z 1;2;3;4;5;6;7;12;120 | |
169 | ||
170 | defines a slat with 4 PCBs : XXYZ | |
171 | ||
172 | The manu to motif relationship is attached to the fact that we're counting | |
173 | counter-clockwise, starting on the lower-left of the PCB. (and the pcb files | |
174 | have to follow this convention to defined their motifs, otherwise all | |
175 | this won't work). | |
176 | ||
177 | Note that the definition of the PCBs have to be in files with extension | |
178 | .pcb (X.pcb, Y.pcb, Z.pcb) | |
179 | ||
180 | ||
59a274b3 | 181 | DetElemIdToBusPatch.dat |
182 | ======================= | |
183 | Lines starting with # are comments. | |
b6e1e92d | 184 | |
59a274b3 | 185 | Contains the detection element identifier with the associated buspatch numbers |
186 | and the corresponding DDL identifier. | |
187 | The link between buspatches and DE's is needed on the rawdata level to identify | |
188 | the type of quadrant/slat to get the corresponding mapping. | |
189 | The DDL id is needed for the rawdata generation only. | |
190 | ||
191 | To generate this file, the macro MUONGenerateBusPatch.C could be used. | |
ecf86371 | 192 | |
67c9732a | 193 | crate.dat |
194 | ========= | |
195 | ||
196 | Muon trigger electronics configuration file (decoded in class | |
197 | AliMUONTriggerCrateStore) directly copy/paste from the ALICE PRR | |
198 | ALICE-EN-2003-010. Gives local board number, name, | |
199 | crate name it belongs to, slot number, and internal switches | |
200 | (used in the algorithm). | |
201 | ||
ecf86371 | 202 | Units used |
203 | ============ | |
204 | ||
205 | Lengths are in centimeters. | |
206 | ||
67c9732a | 207 |