5 \page README_mapping Mapping
8 See the detailed description of the mapping package in ALICE-INT-2003-025.
9 Since that time the mapping has been extended for slat and trigger
10 chamber segmentations an later on also to hold the description of the
11 top level connections of detection elements, including information
12 about DDLs, bus patches and also trigger configuration.
14 \section mapping_s0 Mapping in OCDB
16 The mapping is everywhere in the MUON code loaded from
17 OCDB. In case the mapping data files are changed, the mapping
18 in OCDB has to be regenerated in this way:
21 $> cd $ALICE_ROOT/MUON
22 $> rm Calib/MappingData/Run0_999999999_v0_s0.root
24 root [0] AliMpCDB::WriteMpData();
27 Note that mapping has to be loaded from OCDB almost each time
28 when using MUON classes; the loading of mapping depends on
29 the CBD manager state (the current run number, storage ...).
30 The standard way of loading mapping expects the CDB manager
31 in a state well defined beforehand; this way is used in
35 if ( ! AliMpCDB::LoadDDLStore() ) {
36 AliFatal("Could not access mapping from OCDB !");
40 In the interactive Root session, in case the CDB manager state is
41 not defined, you can load mapping from the local OCDB files in this
44 root [0] AliMpCDB::LoadDDLStore2();
48 \section mapping_s1 Graphical User Interface
50 To use the GUI to plot DE segmentation run:
53 AliMpCDB::LoadDDLStore2();
60 AliMpCDB::LoadDDLStore2();
61 new AliMpDEVisu(w, h);
64 if you want to change the size of the GUI window.
67 w = 1200, h = 600 for PC
68 w = 1000, h = 550 for laptop
72 - drawing motif of a slat/quadrant
73 - search of a given manu (motif) number
74 - draw the channel number for a given manu number by clicking of the motif in canvas
75 - write down in log message informations about the given detection element
77 * number of buspatches, manus, manu serials
78 - option to save log message onto disc
80 \section mapping_s2 Test macros
82 A set of tests macros have been written during the development
83 of the mapping classes. To run these macros:
88 root [0] .x testMacroName.C
92 \section mapping_s3 Data files format
94 \subsection mapping_s3_sub1 zones.dat
96 Describes layout of zones, rows, row segments, subzones, motifs
102 direction of constant pad size (X or Y)
103 offset in X direction
104 offset in Y direction
108 half legth of pad size in x
109 half legth of pad size in y
116 x offset (in number of pads)
117 y offset (in number of pads)
120 first motif position Id
121 step to the next motif position Id (+1 or -1)
125 \subsection mapping_s3_sub2 zones_special.dat
127 Describes layout of special row segments (with irregular motifs)
141 number of these pad rows in row
144 mumber of pads in the rows segment
150 Describes characteristics of the motif type X
160 \subsection mapping_s3_sub3 motifSpecialX.dat
162 Describes characteristics of the special motif with motif Id X;
163 the special motif caontains pads of different size
169 half legth of pad size in x
170 half legth of pad size in y
173 \subsection mapping_s3_sub4 padPosX.dat
175 Maps pad numbers used in the motifX.dat files to
176 the local pad indices (i,j)
186 \subsection mapping_s3_sub5 *.pcb files
188 Lines starting with # are comments.
191 SIZES PadSizeX PadSizeY SizeX SizeY (cm)
193 MOTIF motifType ix iy
194 MOTIF motifType ix iy
198 where ix, iy are the local coordinates (in pad unit) of the
199 lower-left corner of the motif (0,0 is the lower-left corner
202 PCB *MUST* be described in a rotating way, starting lower-left and
203 then counter-clockwise, otherwise the manu-to-motif association
204 (fixed in the slat definition files) will be wrong.
206 Note that for "full" PCBs, the SizeX and SizeY are redundant as they could be
207 computed from the motif alone (but that serves as a cross-check that the motif
208 pattern given is ok). That's not the case for short or rounded PCB though.
211 \subsection mapping_s3_sub6 *.slat files
213 A slat is defined by the list of its PCB, described starting
214 from the beam and going outward.
216 One PCB per line, preceded by the keyword PCB
217 Other lines not matching this syntax are ignored.
218 After the PCB is the list of manu ids for this PCB.
223 PCB X 1-3;24-20;42;44;53
226 PCB Z 1;2;3;4;5;6;7;12;120
229 defines a slat with 4 PCBs : XXYZ
231 The manu to motif relationship is attached to the fact that we're counting
232 counter-clockwise, starting on the lower-left of the PCB. (and the pcb files
233 have to follow this convention to defined their motifs, otherwise all
236 Note that the definition of the PCBs have to be in files with extension
237 .pcb (X.pcb, Y.pcb, Z.pcb)
240 \subsection mapping_s3_sub7 DetElemIdToBusPatch.dat
242 Lines starting with # are comments.
244 Contains the detection element identifier with the associated buspatch numbers
245 and the corresponding DDL identifier.
246 The link between buspatches and DE's is needed on the rawdata level to identify
247 the type of quadrant/slat to get the corresponding mapping.
248 The DDL id is needed for the rawdata generation only.
250 To generate this file, the macro MUONGenerateBusPatch.C could be used.
253 \subsection mapping_s3_sub8 BusPatchSpecial.dat
255 Lines starting with # are comments.
257 Contains the list of bus patches which manu readout is
258 not in the standard order. The format:
261 KEYWORD DDLs BusPatches [ManuIDs}
262 where KEYWORD = REVERT or EXPLICIT
265 - For the bus patches following the REVERT keyword,
266 the manus are just reordered in a reverted order.
267 - For the bus patches following the EXPLICIT keyword,
268 the manus filled with a standard procedure (using the DetElemIdToBusPatch.dat
269 file) are replaced with the list of manus in this file.
272 \subsection mapping_s3_sub9 BusPatchLength.dat
274 Lines starting with # are comments.
276 Contains the list of bus patches and their cable length in meters
286 \subsection mapping_s3_sub10 crate.dat
288 Muon trigger electronics configuration file (decoded in class
289 AliMUONTriggerCrateStore) directly copy/paste from the ALICE PRR
290 ALICE-EN-2003-010. Gives local board number, name,
291 crate name it belongs to, slot number, and internal switches
292 (used in the algorithm).
295 \subsection mapping_s3_sub11 ManuSerialToBin.dat
297 Lines starting with # are comments.
299 Contains the manu serial number with their associated bin number, injection and calibration gain.
301 To compare the bin number with the serial in the CDB database you can run the macro:
304 AliMpCDB::LoadDDLStore2();
305 .L $ALICE_ROOT/MUON/mapping/macros/MUONCheckManu.C+
306 MUONCheckManu(10, kFALSE);
309 The function has two parameters, the first is the number of the chamber (zero mean all chambers).
310 The macro can create a set of histogramms with the different gain distributions stored into a root file
313 Two files a generated: one with the list of manu per detection element with their associated bin and gain
314 value, the other with the bad, strange or unidentified serial number.
317 \section mapping_s4 Units used
319 Lengths are in centimeters.
321 This chapter is defined in the READMEmapping.txt file.