Config.C

diff --git a/MUON/MUONTest.C b/MUON/MUONTest.C
index 4fe380736c77701352a0a759a9c5739f1a157d7b..5ffaaa368616707c4fb31dbda8ccd624d9804f6f 100644 (file)
--- a/MUON/MUONTest.C
+++ b/MUON/MUONTest.C
@@ -28,10 +28,10 @@
 
 void MUONTest(Int_t testNumber)
 {
-  gAlice->Init("./Config_MUON_test.C");
+  gAlice->Init("./Config.C");
   cout << "Init done " << endl;
 
-  AliMUONTest test("./Config_MUON_test.C");
+  AliMUONTest test("./Config.C");
   switch (testNumber) {
     case 1: test.DetElemTransforms();  break;
     case 2: test.ForWhole(kPrintPads); break; 

diff --git a/MUON/README b/MUON/README
index 43bcc524502d696023ca91e6c3b91eb6a5e49db3..487e4df7040984896267a08fa3adbb6d4dd693e3 100644 (file)
--- a/MUON/README
+++ b/MUON/README
@@ -24,7 +24,7 @@ reconstruction and macro analysis
  How to run a MUON generation
 ==========================================================
 aliroot
-root [0] gAlice->Run(10,"$ALICE_ROOT/MUON/Config_MUON_test.C");
+root [0] gAlice->Run(10,"$ALICE_ROOT/MUON/Config.C");
 
 1 single muon of 7 GeV/c in the MUON spectrometer 
 acceptance will be simulated using geant3. 
@@ -69,7 +69,7 @@ MUONTestTrigger() or MUONTestTrigger("galice.root",##) for the event number ##
 ============================================================
  How to check the Geometry
 ============================================================
-gAlice->Init("$ALICE_ROOT/MUON/Config_MUON_test.C");
+gAlice->Init("$ALICE_ROOT/MUON/Config.C");
 .L $ALICE/geant3/TGeant3/G3GUI.C
 G3GUI()
 
@@ -213,7 +213,36 @@ To compile MUONTracker.C
 
 // To run MUONTracker
 MUONTracker(iEventMin,iEventMax,"galice.root"); // iEventMin: first event
-                                               // iEventMax: last event        
+
+===========================================================
+ Macro  MUONGenerateGeometryData.C
+===========================================================
+                                               
+Macro for generating the geometry data files:
+(transform_*.dat, svmap_*.dat).
+- MUON/data/transform_*dat files contain all the information 
+about the transformation (traslation + rotation) needed for 
+the positionning of each detection element of the MUON
+spectrometer.
+- MUON/data/svmap_*.dat files contain all the information to link 
+each geant volume (it can be extended to other virtual MC) with
+a detection element. The point here is that a given detection
+element, i.e. a slat chamber consists of many geant volumes.
+the correspondence is then defined in an input file.
+Eanch time there is a change in the virtual MC geometry, these
+input files must be re-generated via the macro  
+MUONGenerateGeometryData.C
+
+To be run from aliroot:
+.x MUONGenerateGeometryData.C
+
+The generated files do not replace the existing ones
+but have different names (with extension ".out").
+To compare/replace the existing files with generated ones
+run the scripts in MUON/data:
+compare_data [transform] [svmaps ]
+reset_data [transform] [svmaps]
+Author: I. Hrivnacova, IPN Orsay
 
 
 ===========================================================