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 ##
83 ============================================================
84 How to check the Geometry
85 ============================================================
86 gAlice->Init("$ALICE_ROOT/MUON/Config.C");
87 .L $ALICE/geant3/TGeant3/G3GUI.C
90 ============================================================
91 How to check the Geometry with the new Geometrical modeler
92 ftp://root.cern.ch/root/doc/chapter16.pdf
93 http://agenda.cern.ch/fullAgenda.php?ida=a05212
94 ============================================================
95 gAlice->Init("$ALICE_ROOT/MUON/Config.C");
96 gGeoManager->GetMasterVolume()->Draw();
99 ============================================================
100 How to run MUONdisplay
101 ============================================================
102 First you need to perform a full simulation:
103 generation, digitalisation and clusterisation
104 .L $ALICE_ROOT/MUON/MUONdisplay.C
105 MUONdisplay(0,"galice.root")
107 ============================================================
108 Tracking parameters, cuts, energy loss and physics processes
109 ============================================================
110 Tracking parameters in MUON are automatically defined by GEANT
111 MUON takes the default values of CUTs and physics processes
112 defined by the Config files, except for the gas mixture medium
113 of the tracking chambers. The CUT's and physics processes of
114 the gas mixture medium is then defined in the galice.cuts file
115 in the data directory. In particular ILOSS parameter MUST be
116 equal unity (1) in order simulate a realistic energy loss
117 distribution (mean value and fluctuations) in the active gas.
119 ============================================================
120 Tracking of particle in the magnetic field
121 ============================================================
122 GEANT has two ways for tracking charged particles in the
123 magnetic field: HELIX et RKUTA.
124 HELIX is faster and works well if the gradient of magnetic
126 For MUON, HELIX is a not a good approximation and we must
127 use RKUTA to get the optimal mass resolution of the
128 spectrometer. The choice of HELIX or RKUTA is done in the
129 config file when the magnetic field is defined:
130 AliMagFMaps* field = new AliMagFMaps("Maps","Maps", TRACKING, FACTOR, MAXB, AliMagFMaps::k4kG);
131 gAlice->SetField(field);
132 TRACKING must be 1 for RKUTA and 2 for HELIX (the default value for aliroot is 2 (HELIX))
133 FACTOR allows you to set the magnetic field to 0, just putting FACTOR=0. Default value is 1.
134 MAXB is the maximum magnetic field which is 10.T
136 ===========================================================
137 MUON cocktail for physics ..............
138 ===========================================================
139 There is a MUON cocktail generator of the muon sources in the
140 EVGEN directory. This class derives from AliGenCocktail.
141 In the init of this class I have filled the cocktail with
142 the muon sources: J/Psi, Upsilon, Open Charm, Open Beauty,
143 Pion, Kaons. The code needs only the production cross section
144 at 4pi (for the moment this values are in the code since I
145 prefere them do not be modified), and the code calculates the
146 rate of particles in the acceptance, making the scaling based
147 on the number of collisions for the hard probes and on the
148 number of participants for soft sources: Pions and Kaons.
150 In the Genereate of this class all entries in the cocktail
151 are called and we define a "primordial trigger" with requires
152 a minimum number of muons above a Pt cut in the required acceptance.
153 In order to normalized to the real number of simulated events,
154 there are 2 data members in the class fNsuceeded adn fNGenerate
155 which tell us what is the biais source.
157 Enclose an example to use this generator:
158 AliGenMUONCocktail * gener = new AliGenMUONCocktail();
159 gener->SetPtRange(1.,100.); // Transverse momentum range
160 gener->SetPhiRange(0.,360.); // Azimuthal angle range
161 gener->SetYRange(-4.0,-2.4);
162 gener->SetMuonPtCut(1.);
163 gener->SetMuonThetaCut(171.,178.);
164 gener->SetMuonMultiplicity(2);
165 gener->SetImpactParameterRange(0.,5.); // 10% most centra PbPb collisions
166 gener->SetVertexSmear(kPerTrack);
167 gener->SetOrigin(0,0,0); // Vertex position
168 gener->SetSigma(0,0,0.0); // Sigma in (X,Y,Z) (cm) on IP position
171 ===========================================================
172 csh Script for the full reconstruction with raw data generator
173 ===========================================================
174 See file AlirootRun_MUONtest.script
178 ============================================================
179 How to run MUONRecoCheck macro
180 ============================================================
181 To check the muon reconstruction by comparing the reconstructed tracks
182 with the reference tracks made of "AliTrackReference" for the hits and
183 kinematic informations (TParticle) for the vertex.
184 This macro can be used to check the track reconstruction e.g. efficiency,
185 momentum resolution ... but also to make physics analysis whenever
186 track identification is needed.
188 To compile MUONRecoCheck.C
189 .includepath $ALICE_ROOT/STEER
190 .includepath $ALICE_ROOT/MUON
191 .L $ALICE_ROOT/MUON/MUONRecoCheck.C+
193 // To run MUONRecoCheck
194 MUONRecoCheck(nEvent,"galice.root"); // nEvent = nb of events
197 ============================================================
198 How to run MUONTracker macro
199 ============================================================
200 To make the track reconstruction directly from AliTrackReference hits
201 which are recorded in TrackRefs.root during the simulation.
202 It can be used to check the reconstruction without clusterization.
204 To compile MUONTracker.C
205 .includepath $ALICE_ROOT/STEER
206 .includepath $ALICE_ROOT/MUON
207 .L $ALICE_ROOT/MUON/MUONTracker.C+
209 // To run MUONTracker
210 MUONTracker(iEventMin,iEventMax,"galice.root"); // iEventMin: first event
212 ===========================================================
213 Macro MUONGenerateGeometryData.C
214 ===========================================================
216 Macro for generating the geometry data files:
217 (transform_*.dat, svmap_*.dat).
218 - MUON/data/transform_*dat files contain all the information
219 about the transformation (traslation + rotation) needed for
220 the positionning of each detection element of the MUON
222 - MUON/data/svmap_*.dat files contain all the information to link
223 each geant volume (it can be extended to other virtual MC) with
224 a detection element. The point here is that a given detection
225 element, i.e. a slat chamber consists of many geant volumes.
226 the correspondence is then defined in an input file.
227 Eanch time there is a change in the virtual MC geometry, these
228 input files must be re-generated via the macro
229 MUONGenerateGeometryData.C
231 To be run from aliroot:
232 .x MUONGenerateGeometryData.C
234 The generated files do not replace the existing ones
235 but have different names (with extension ".out").
236 To compare/replace the existing files with generated ones
237 run the scripts in MUON/data:
238 compare_data [transform] [svmaps ]
239 reset_data [transform] [svmaps]
240 Author: I. Hrivnacova, IPN Orsay
243 ===========================================================
244 Still working ..............
245 ===========================================================