AliHLTTPCCAMerger.cxx added to compilation

[u/mrichter/AliRoot.git] / MUON / READMEgeometry.txt

diff --git a/MUON/READMEgeometry.txt b/MUON/READMEgeometry.txt
index 1b0dea5b15d2bb3fad159d7a925bae18464afe49..271b2d6cb3fd64219d126e86be7c1456db2f59bd 100644 (file)
--- a/MUON/READMEgeometry.txt
+++ b/MUON/READMEgeometry.txt
@@ -40,29 +40,47 @@ file.
 \see http://agenda.cern.ch/fullAgenda.php?ida=a05212
 
 <pre>
-AliMpCDB::LoadMpSegmentation2(); 
-gAlice->Init("$ALICE_ROOT/MUON/Config.C");
+TGeoManager::Import("geometry.root");
 gGeoManager->GetMasterVolume()->Draw();
 </pre>
 
+A helper macro for adding and removing volumes in the
+scene, MUONGeometryViewingHelper.C is also available.
+ 
+
 \section geometry_s3  How to check the overlaps with the Root geometrical modeler
 
 \see  ftp://root.cern.ch/root/doc/chapter16.pdf
 \see  http://agenda.cern.ch/fullAgenda.php?ida=a05212
 
 <pre>
-AliMpCDB::LoadMpSegmentation2(); 
-gAlice->Init("$ALICE_ROOT/MUON/Config.C");
-gGeoManager->CheckOverlaps();
+TGeoManager::Import("geometry.root");
+gGeoManager->CheckOverlaps(0.001);
 gGeoManager->PrintOverlaps();
 </pre>
 
 More extensive, but also more time consuming checking,
 can be performed in this way:
 <pre>
-gGeoManager->CheckGeometryFull();
+gGeoManager->CheckGeometryFull(1000000,0,0,0,"o"); >& check_full.out
 </pre>
-
+Then, you will find in the output file \em check_full.out the list of
+volumes where any overlaps have been detected. As TGeoManager
+does not remember all overlaps found during checking,
+in order to investigate them, one has to re-run the checking for 
+each listed volume:
+<pre>
+gGeoManager->FindVolumeFast("MyVolume")->CheckOverlaps(0.001, "s");
+gGeoManager->PrintOverlaps(); >& overlaps_MyVolume.txt 
+</pre>
+At this stage the overlaps found for the selected volume can be also browsed 
+with TBrowser. Sometimes it happens that the reported overlapping
+volumes are assemblies and nothing is visualized on the scene
+when clicking on the overlap icon in the browser.
+In this case you can use the function setDaughtersVisibility()
+from the MUONGeometryViewingHelper.C macro, which propagates the
+visibility setting through all assembly levels up to the real
+volumes.
 
 \section geometry_s4 Macro  MUONGenerateGeometryData.C
                                                
@@ -161,10 +179,15 @@ afterwards.
 The macro MUONCheckMisAligner.C performs the misalignment on an existing muon 
 arm geometry based on the standard definition of the detector elements.
 
+To be run from aliroot:
+<pre>
+AliMpCDB::LoadMpSegmentation2();
+.x MUONCheckMisAligner.C
+</pre>
+
 It uses AliMUONGeometryAligner : 
 - Creates a new AliMUONGeometryTransformer and AliMUONGeometryAligner
-- Reads the transformations in from the transform.dat file (make sure that
-this file is the _standard_ one by comparing it to the one in CVS)
+- Loads the geometry from the specified geometry file (default is geometry.root)
 - Creates a second AliMUONGeometryTransformer by misaligning the existing 
 one using AliMUONAligner::MisAlign