DP: xz CPV-EMC distance filled to TS

[u/mrichter/AliRoot.git] / MUON / READMEmapping

diff --git a/MUON/READMEmapping b/MUON/READMEmapping
index 367fd902d96d2259f592d467bdec09347a9dd705..3ffb862313386e485c0cf9fdbf551762d5b4b9aa 100644 (file)
--- a/MUON/READMEmapping
+++ b/MUON/READMEmapping
@@ -6,6 +6,30 @@
  
  See detailed description in ALICE-INT-2003-025.
 
+ Graphical User Interface
+ ========================
+  
+  To use the GUI to plot DE segmentation run:
+  
+  new AliMpDEVisu();
+  or 
+  
+  new AliMpDEVisu(w, h);
+  
+  if you want to change the size of the GUI window.
+  Typical value are:
+    w = 1200, h = 600 for PC
+    w = 1000, h = 550 for laptop
+
+  The GUI allows:
+  - drawing motif of a slat/quadrant
+  - search of a given manu (motif) number
+  - draw the channel number for a given manu number by clicking of the motif in canvas
+  - write down in log message informations about the given detection element
+    * DE Id, DE name, 
+    * number of buspatches, manus, manu serials
+  - option to save log message onto disc
+
  Test macros
  ============
    cd ../mapping/macro
@@ -43,7 +67,7 @@
    
 
   Data files format
-  ============
+  =================
 
   zones.dat:
   -------------
@@ -53,6 +77,8 @@
     number of zones  
     number of rows  
     direction of constant pad size (X or Y)
+    offset in X direction
+    offset in Y direction
   
   ZONE     
     number of zone  
@@ -124,5 +150,82 @@
     pad index i (in x)
     pad index j (in y)
   
+
+  *.pcb files
+  ============
+
+  Lines starting with # are comments.
+
+  SIZES PadSizeX PadSizeY SizeX SizeY (cm)
+
+  MOTIF motifType ix iy
+  MOTIF motifType ix iy
+  ...
+
+  where ix, iy are the local coordinates (in pad unit) of the
+  lower-left corner of the motif (0,0 is the lower-left corner
+  of the PCB).
+
+  PCB *MUST* be described in a rotating way, starting lower-left and 
+  then counter-clockwise, otherwise the manu-to-motif association 
+  (fixed in the slat definition files) will be wrong.
+
+  Note that for "full" PCBs, the SizeX and SizeY are redundant as they could be 
+  computed from the motif alone (but that serves as a cross-check that the motif 
+  pattern given is ok). That's not the case for short or rounded PCB though.
+
+  *.slat files
+  =============
+
+  A slat is defined by the list of its PCB, described starting 
+  from the beam and going outward.
+
+  One PCB per line, preceded by the keyword PCB
+  Other lines not matching this syntax are ignored.
+  After the PCB is the list of manu ids for this PCB.
+ 
+  Example :
+
+  PCB X 1-3;24-20;42;44;53
+  PCB X 1-14
+  PCB Y 100-90
+  PCB Z 1;2;3;4;5;6;7;12;120
+
+  defines a slat with 4 PCBs : XXYZ
+
+  The manu to motif relationship is attached to the fact that we're counting 
+  counter-clockwise, starting on the lower-left of the PCB. (and the pcb files 
+  have to follow this convention to defined their motifs, otherwise all 
+  this won't work).
+
+  Note that the definition of the PCBs have to be in files with extension
+  .pcb (X.pcb, Y.pcb, Z.pcb)
+
+  
+  DetElemIdToBusPatch.dat
+  =======================
+  Lines starting with # are comments.
   
+  Contains the detection element identifier with the associated buspatch numbers 
+  and the corresponding DDL identifier.
+  The link between buspatches and DE's is needed on the rawdata level to identify 
+  the type of quadrant/slat to get the corresponding mapping.
+  The DDL id is needed for the rawdata generation only.
+
+  To generate this file, the macro MUONGenerateBusPatch.C could be used.
+
+  crate.dat
+  =========
+  
+  Muon trigger electronics configuration file (decoded in class 
+  AliMUONTriggerCrateStore) directly copy/paste from the ALICE PRR 
+  ALICE-EN-2003-010. Gives local board number, name, 
+  crate name it belongs to, slot number, and internal switches 
+  (used in the algorithm).
+
+  Units used
+  ============
+ 
+  Lengths are in centimeters.
+