1 /**************************************************************************
2 * Copyright(c) 1998-1999, ALICE Experiment at CERN, All rights reserved. *
4 * Author: The ALICE Off-line Project. *
5 * Contributors are mentioned in the code where appropriate. *
7 * Permission to use, copy, modify and distribute this software and its *
8 * documentation strictly for non-commercial purposes is hereby granted *
9 * without fee, provided that the above copyright notice appears in all *
10 * copies and that both the copyright notice and this permission notice *
11 * appear in the supporting documentation. The authors make no claims *
12 * about the suitability of this software for any purpose. It is *
13 * provided "as is" without express or implied warranty. *
14 **************************************************************************/
18 ==========================================================
19 Please add to this README file all information concerning
20 config files, simulation, digitalization, clusterization,
21 reconstruction and macro analysis
23 ==========================================================
24 How to check that your aliroot is working well
25 ==========================================================
26 There is a script file AlirootRun_MUONtest.script which
27 allows for simulating, reconstructing and making the
28 invariant analysis of the generated Upsilon (1S).
29 The used configuration file is Config.C in MUON
31 There you have to type :
33 source $ALICE_ROOT/MUON/AlirootRun_MUONtest.script
35 If you do not recover a few Upsilons in their mass region
36 in the file MUONmassPlot.root
38 ==========================================================
39 How to run a MUON generation
40 ==========================================================
42 root [0] gAlice->Run(10,"$ALICE_ROOT/MUON/Config.C");
44 1 single muon of 7 GeV/c in the MUON spectrometer
45 acceptance will be simulated using geant3.
46 Hit information will be store in the root file in the
48 If you want to change the option or to define a new directory
49 for hits, you have to do the following before:
50 root [0] gAlice->SetConfigFunction("Config( \"/home/martinez/aliroot/work_NewIO/test/\" , \"box\" );");
52 ============================================================
53 How to run MUONCheck macro
54 ============================================================
55 To check the content of a root data file, the MUONCheck
56 provides a ascii output on screen.
58 To compile MUONCheck.C
59 .includepath $ALICE_ROOT/STEER
60 .includepath $ALICE_ROOT/MUON
61 .L $ALICE_ROOT/MUON/MUONCheck.C++
63 gSystem->Load("$ALICE_ROOT/MUON/MUONCheck_C.so")
65 To print Kine : (default file is galice.root )
66 MUONkine() or MUONkine("galice.root",##) for the event number ##
68 To print hits : (default file is galice.root if not MUONhits("toto.root""); )
69 MUONhits() or MUONhits("galice.root",##) for the event number ##
71 To print digits : (default file is galice.root)
72 MUONdigits() or MUONdigits("galice.root",##) for the event number ##
74 To print rawcluster : (default file is galice.root)
75 MUONrecpoints() or MUONrecpoints("galice.root",##) for the event number ##
77 To print trigger : (default file is galice.root)
78 MUONTestTrigger() or MUONTestTrigger("galice.root",##) for the event number ##
82 ============================================================
83 How to check the Geometry
84 ============================================================
85 gAlice->Init("$ALICE_ROOT/MUON/Config.C");
86 .L $ALICE/geant3/TGeant3/G3GUI.C
89 ============================================================
90 How to check the Geometry with the new Geometrical modeler
91 ftp://root.cern.ch/root/doc/chapter16.pdf
92 http://agenda.cern.ch/fullAgenda.php?ida=a05212
93 ============================================================
94 gAlice->Init("$ALICE_ROOT/MUON/Config.C");
95 gGeoManager->GetMasterVolume()->Draw();
98 ============================================================
99 How to run MUONdisplay
100 ============================================================
101 First you need to perform a full simulation:
102 generation, digitalisation and clusterisation
103 To run MUONdisplay with Root 5.04/00 you need to get a fix in
104 the gpad/src/TPad.cxx from Root CVS:
105 cvs update -r 1.200 gpad/src/TPad.cxx
108 .L $ALICE_ROOT/MUON/MUONdisplay.C
109 MUONdisplay(0,"galice.root")
111 ============================================================
112 Tracking parameters, cuts, energy loss and physics processes
113 ============================================================
114 Tracking parameters in MUON are automatically defined by GEANT
115 MUON takes the default values of CUTs and physics processes
116 defined by the Config files, except for the gas mixture medium
117 of the tracking chambers. The CUT's and physics processes of
118 the gas mixture medium is then defined in the galice.cuts file
119 in the data directory. In particular ILOSS parameter MUST be
120 equal unity (1) in order simulate a realistic energy loss
121 distribution (mean value and fluctuations) in the active gas.
123 ============================================================
124 Tracking of particle in the magnetic field
125 ============================================================
126 GEANT has two ways for tracking charged particles in the
127 magnetic field: HELIX et RKUTA.
128 HELIX is faster and works well if the gradient of magnetic
130 For MUON, HELIX is a not a good approximation and we must
131 use RKUTA to get the optimal mass resolution of the
132 spectrometer. The choice of HELIX or RKUTA is done in the
133 config file when the magnetic field is defined:
134 AliMagFMaps* field = new AliMagFMaps("Maps","Maps", TRACKING, FACTOR, MAXB, AliMagFMaps::k4kG);
135 gAlice->SetField(field);
136 TRACKING must be 1 for RKUTA and 2 for HELIX (the default value for aliroot is 2 (HELIX))
137 FACTOR allows you to set the magnetic field to 0, just putting FACTOR=0. Default value is 1.
138 MAXB is the maximum magnetic field which is 10.T
140 ===========================================================
141 MUON cocktail for physics ..............
142 ===========================================================
143 There is a MUON cocktail generator of the muon sources in the
144 EVGEN directory. This class derives from AliGenCocktail.
145 In the init of this class I have filled the cocktail with
146 the muon sources: J/Psi, Upsilon, Open Charm, Open Beauty,
147 Pion, Kaons. The code needs only the production cross section
148 at 4pi (for the moment this values are in the code since I
149 prefere them do not be modified), and the code calculates the
150 rate of particles in the acceptance, making the scaling based
151 on the number of collisions for the hard probes and on the
152 number of participants for soft sources: Pions and Kaons.
154 In the Genereate of this class all entries in the cocktail
155 are called and we define a "primordial trigger" with requires
156 a minimum number of muons above a Pt cut in the required acceptance.
157 In order to normalized to the real number of simulated events,
158 there are 2 data members in the class fNsuceeded adn fNGenerate
159 which tell us what is the biais source.
161 Enclose an example to use this generator:
162 AliGenMUONCocktail * gener = new AliGenMUONCocktail();
163 gener->SetPtRange(1.,100.); // Transverse momentum range
164 gener->SetPhiRange(0.,360.); // Azimuthal angle range
165 gener->SetYRange(-4.0,-2.4);
166 gener->SetMuonPtCut(1.);
167 gener->SetMuonThetaCut(171.,178.);
168 gener->SetMuonMultiplicity(2);
169 gener->SetImpactParameterRange(0.,5.); // 10% most centra PbPb collisions
170 gener->SetVertexSmear(kPerTrack);
171 gener->SetOrigin(0,0,0); // Vertex position
172 gener->SetSigma(0,0,0.0); // Sigma in (X,Y,Z) (cm) on IP position
175 ================================================================
176 csh Script for the full reconstruction with raw data generator
177 ================================================================
178 The rawdata generation and analysis is working with the new segmentation.
179 So the config file must use the version "AliMUONFactoryV3"
182 The method AliSimulation::SetWriteRawData("MUON") enables on
183 the muon rawdata generation
185 AliSimulation MuonSim("$ALICE_ROOT/MUON/Config.C")
186 MuonSim.SetWriteRawData("MUON")
193 AliReconstruction MuonRec("galice.root");
194 MuonRec.SetInput("$YOUR_WORKING_DIRECTORY/"); Do not forget the slash at the end!
195 MuonRec.SetRunVertexFinder(kFALSE);
196 MuonRec.SetRunLocalReconstruction("MUON");
197 MuonRec.SetRunTracking("");
198 MuonRec.SetFillESD("MUON");
205 ============================================================
206 How to run MUONRecoCheck macro
207 ============================================================
208 To check the muon reconstruction by comparing the reconstructed tracks
209 with the reference tracks made of "AliTrackReference" for the hits and
210 kinematic informations (TParticle) for the vertex.
211 This macro can be used to check the track reconstruction e.g. efficiency,
212 momentum resolution ... but also to make physics analysis whenever
213 track identification is needed.
215 To compile MUONRecoCheck.C
216 .includepath $ALICE_ROOT/STEER
217 .includepath $ALICE_ROOT/MUON
218 .L $ALICE_ROOT/MUON/MUONRecoCheck.C+
220 // To run MUONRecoCheck
221 MUONRecoCheck(nEvent,"galice.root"); // nEvent = nb of events
224 ============================================================
225 How to run MUONTracker macro
226 ============================================================
227 To make the track reconstruction directly from AliTrackReference hits
228 which are recorded in TrackRefs.root during the simulation.
229 It can be used to check the reconstruction without clusterization.
231 To compile MUONTracker.C
232 .includepath $ALICE_ROOT/STEER
233 .includepath $ALICE_ROOT/MUON
234 .L $ALICE_ROOT/MUON/MUONTracker.C+
236 // To run MUONTracker
237 MUONTracker(iEventMin,iEventMax,"galice.root"); // iEventMin: first event
239 ===========================================================
240 Macro MUONGenerateGeometryData.C
241 ===========================================================
243 Macro for generating the geometry data files:
244 (transform_*.dat, svmap_*.dat).
245 - MUON/data/transform_*dat files contain all the information
246 about the transformation (traslation + rotation) needed for
247 the positionning of each detection element of the MUON
249 - MUON/data/svmap_*.dat files contain all the information to link
250 each geant volume (it can be extended to other virtual MC) with
251 a detection element. The point here is that a given detection
252 element, i.e. a slat chamber consists of many geant volumes.
253 the correspondence is then defined in an input file.
254 Eanch time there is a change in the virtual MC geometry, these
255 input files must be re-generated via the macro
256 MUONGenerateGeometryData.C
258 To be run from aliroot:
259 .x MUONGenerateGeometryData.C
261 The generated files do not replace the existing ones
262 but have different names (with extension ".out").
263 To compare/replace the existing files with generated ones
264 run the scripts in MUON/data:
265 compare_data.sh [transform] [svmap ]
266 reset_data.sh [transform] [svmap ]
267 Author: I. Hrivnacova, IPN Orsay
270 ===========================================================
271 Still working ..............
272 ===========================================================