Updating info on the MUONGenerateGeometryData.C macro

diff --git a/MUON/README b/MUON/README
index 59ea947516534c5a99835fbbc144fae322e89309..4ebe8c122f4c2b6ddc3bb5271d3a45ac4e3cceec 100644 (file)
--- a/MUON/README
+++ b/MUON/README
@@ -243,17 +243,17 @@ MUONTracker(iEventMin,iEventMax,"galice.root"); // iEventMin: first event
 ===========================================================
                                                
 Macro for generating the geometry data files:
-(transform_*.dat, svmap_*.dat).
-- MUON/data/transform_*dat files contain all the information 
+(transform.dat, svmap.dat).
+- MUON/data/transform.dat file contains 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 
+- MUON/data/svmap.dat file contains 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
+Each time there is a change in the definition of MC geometry, these
 input files must be re-generated via the macro  
 MUONGenerateGeometryData.C
 
@@ -262,11 +262,7 @@ To be run from aliroot:
 
 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.sh [transform] [svmap ]
-reset_data.sh [transform] [svmap ]
-Author: I. Hrivnacova, IPN Orsay
+Replacement with new files has to be done manually.
 
 
 ==========================================================