==========================================================
How to check that your aliroot is working well
==========================================================
-There is a script file AlirootRun_MUONtest.script which
+There is a script file AlirootRun_MUONtest.sh which
allows for simulating, reconstructing and making the
invariant analysis of the generated Upsilon (1S).
The used configuration file is Config.C in MUON
directory.
-There you have to type :
+You have to type :
+source $ALICE_ROOT/MUON/AlirootRun_MUONtest.sh
+The results of this test are saved in test_out/ directory.
+Please note that the CDB (Condition DataBase) is now always *required*
+to perform either simulation or reconstruction. For the moment, a version
+ of that CDB is stored in CVS, so you should have one already in MUON/Calib
+subdirectories.
-source $ALICE_ROOT/MUON/AlirootRun_MUONtest.script
+==========================================================
+ How to check that your aliroot is working VERY well
+==========================================================
+There is a script file AlirootRun_MUONlongtest.sh which
+allows for simulating, reconstructing and making the
+-+invariant analysis of the generated Upsilon (1S).
+This script generates a large number of Upsilon (20k)
+in order to access differential quantities.
+The used configuration file is Config.C in MUON
+directory.
+One should really run this script to check if the MUON
+code can process a large number of events WITHOUT errors,
+in particular before making important commits !!
+
+You have to type :
+$ALICE_ROOT/MUON/AlirootRun_MUONtestlong.sh
+The results of this test are saved in testlong_out/ directory
+and will be kept in CVS
-If you do not recover a few Upsilons in their mass region
-in the file MUONmassPlot.root
+(NOTE: the macros performing the calculations/plots MUONefficiency.C
+and MUONplotEfficiency.C are also able to handle J/Psi if
+Config.C is modified accordingly )
==========================================================
How to run a MUON generation
gSystem->Load("$ALICE_ROOT/MUON/MUONCheck_C.so")
To print Kine : (default file is galice.root )
-MUONkine() or MUONkine("galice.root",##) for the event number ##
+MUONkine() or MUONkine(##,"galice.root") for the event number ##
To print hits : (default file is galice.root if not MUONhits("toto.root""); )
-MUONhits() or MUONhits("galice.root",##) for the event number ##
+MUONhits() or MUONhits(##,"galice.root") for the event number ##
To print digits : (default file is galice.root)
-MUONdigits() or MUONdigits("galice.root",##) for the event number ##
+MUONdigits() or MUONdigits(##,"galice.root") for the event number ##
+
+To print sdigits : (default file is galice.root)
+MUONsdigits() or MUONsdigits(##,"galice.root") for the event number ##
To print rawcluster : (default file is galice.root)
-MUONrecpoints() or MUONrecpoints("galice.root",##) for the event number ##
+MUONrecpoints() or MUONrecpoints(##,"galice.root") for the event number ##
To print trigger : (default file is galice.root)
-MUONrectrigger() or MUONrectrigger("galice.root",##) for the event number ##
+MUONrectrigger() or MUONrectrigger(##,"galice.root") for the event number ##
....
============================================================
- How to check the Geometry
+ How to check the Geometry with the new Geometrical modeler
+ ftp://root.cern.ch/root/doc/chapter16.pdf
+ http://agenda.cern.ch/fullAgenda.php?ida=a05212
============================================================
gAlice->Init("$ALICE_ROOT/MUON/Config.C");
-.L $ALICE/geant3/TGeant3/G3GUI.C
-G3GUI()
+gGeoManager->GetMasterVolume()->Draw();
+
============================================================
- How to check the Geometry with the new Geometrical modeler
+ How to check the overlap with the new Geometrical modeler
ftp://root.cern.ch/root/doc/chapter16.pdf
http://agenda.cern.ch/fullAgenda.php?ida=a05212
============================================================
gAlice->Init("$ALICE_ROOT/MUON/Config.C");
-gGeoManager->GetMasterVolume()->Draw();
-
+gGeoManager->CheckOverlaps();
+gGeoManager->PrintOverlaps();
============================================================
How to run MUONdisplay
MuonRec.SetRunLocalReconstruction("MUON");
MuonRec.SetRunTracking("");
MuonRec.SetFillESD("MUON");
-MuonRec.SetOption("MUON", "AZ Kalman"); // to use AZ clustering and Kalman filter
-MuonRec.Run();
+MuonRec.SetOption("MUON", "VS"); // to use VS cluster finder
+// MuonRec.SetOption("MUON", "VS Original"); // to run VS and original track finder
+// MuonRec.SetOption("MUON", "Combi"); // to run combined cluster / track finder
+MMuonRec.Run();
.q
EOF
===========================================================
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
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.
+
+
+==========================================================
+ How to Merge events
+==========================================================
+
+You can merge 2 types of simulated events. For example,
+you can simulate Hijing events, and then simulate muons
+merging both.
+
+Merging is done at the sdigits level, so Kinematics files
+of the merged events will just correspond to the
+Config.C simulated file (not to Config_HIJING.C).
+
+You must, first, do the Hijing simulation and store it
+in directory $HIJING_SIM. Note that for merging you
+won't need Kinematics files of the Hijing simulation...
+
+Hijing simulation
+
+aliroot -b << EOF
+AliSimulation HijingSim("$HIJING_SIM/Config_HIJING.C")
+HijingSim.Run(5)
+.q
+EOF
+
+
+Then you can do muon simulation and reconstruction
+merging both simulated events. In next example, we are
+merging 20 times each Hijing event in order to simulate
+100 muons merged with 5 Hijing events.
+
+
+aliroot -b << EOF
+AliSimulation MuonSim("$ALICE_ROOT/MUON/Config.C")
+MuonSim.MergeWith("$HIJING_SIM/galice.root",20) //parameters are the Hijing simulation file and the number of times we use each Hijing event
+MuonSim.Run(100) // number of muon (Config.C) events
+.q
+EOF
+
+
+aliroot -b << EOF
+TPluginManager * pluginmanager = gROOT->GetPluginManager()
+pluginmanager->AddHandler("AliReconstructor","MUON","AliMUONReconstructor","MUON","AliMUONReconstructor()")
+AliReconstruction MuonRec("galice.root")
+MuonRec.SetRunTracking("")
+MuonRec.SetRunVertexFinder(kFALSE)
+MuonRec.SetRunLocalReconstruction("MUON")
+MuonRec.SetFillESD("MUON")
+MuonRec.Run()
+.q
+EOF
+
+==========================================================
+ How to play with the CDB
+==========================================================
+If you'd like to see how the CDB is created, please have a look at the
+MUONCDB.C (work in progress, though).
===========================================================
Still working ..............
git://git.uio.no / u / mrichter / AliRoot.git / blobdiff