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