7 See detailed description in ALICE-INT-2003-025.
13 root [0] .x testMacroName.C
14 - see available macros below
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
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
24 Macros included in the test suite:
33 testSectorPadIterators.C
34 testMotifTypeIterators.C
35 testNeighboursPadIterator.C
38 testPlaneAreaIterator.C
40 Other macros (not included in the test suite):
42 testUpdateGlobalIndices.C
50 Describes layout of zones, rows, row segments, subzones, motifs
55 direction of constant pad size (X or Y)
61 half legth of pad size in x
62 half legth of pad size in y
69 x offset (in number of pads)
70 y offset (in number of pads)
73 first motif position Id
74 step to the next motif position Id (+1 or -1)
78 Describes layout of special row segments (with irregular motifs)
91 number of these pad rows in row
94 mumber of pads in the rows segment
100 Describes characteristics of the motif type X
110 Describes characteristics of the special motif with motif Id X;
111 the special motif caontains pads of different size
116 half legth of pad size in x
117 half legth of pad size in y
121 Maps pad numbers used in the motifX.dat files to
122 the local pad indices (i,j)
133 Lines starting with # are comments.
135 SIZES PadSizeX PadSizeY SizeX SizeY (cm)
137 MOTIF motifType ix iy
138 MOTIF motifType ix iy
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
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.
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.
156 A slat is defined by the list of its PCB, described starting
157 from the beam and going outward.
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.
165 PCB X 1-3;24-20;42;44;53
168 PCB Z 1;2;3;4;5;6;7;12;120
170 defines a slat with 4 PCBs : XXYZ
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
177 Note that the definition of the PCBs have to be in files with extension
178 .pcb (X.pcb, Y.pcb, Z.pcb)
181 DetElemIdToBusPatch.dat
182 =======================
183 Lines starting with # are comments.
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.
191 To generate this file, the macro MUONGenerateBusPatch.C could be used.
196 Lengths are in centimeters.