Removing output of hit pointers in AliMUONTrack class. New switch in ALiMUONv1 for...
[u/mrichter/AliRoot.git] / MUON / README
CommitLineData
50837721 1/**************************************************************************
2 * Copyright(c) 1998-1999, ALICE Experiment at CERN, All rights reserved. *
3 * *
4 * Author: The ALICE Off-line Project. *
5 * Contributors are mentioned in the code where appropriate. *
6 * *
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 **************************************************************************/
15
16/* $Id$ */
17
88cb7938 18==========================================================
19Please add to this README file all information concerning
20config files, simulation, digitalization, clusterization,
21reconstruction and macro analysis
22
23==========================================================
7985603c 24 How to run a MUON generation
88cb7938 25==========================================================
26aliroot
27root [0] gAlice->Run(10,"$ALICE_ROOT/MUON/Config_MUON_test.C");
28
291 single muon of 7 GeV/c in the MUON spectrometer
30acceptance will be simulated using geant3.
31Hit information will be store in the root file in the
32execution directory.
88cb7938 33If you want to change the option or to define a new directory
34for hits, you have to do the following before:
35root [0] gAlice->SetConfigFunction("Config( \"/home/martinez/aliroot/work_NewIO/test/\" , \"box\" );");
36
37============================================================
38 How to run MUON Digitalization
39============================================================
40To process the digitalization of hits the AliRunDigitizer
41framework is used:
42
2058bf30 43AliRunDigitizer * manager = new AliRunDigitizer(1,1);
44manager->SetInputStream(0,"galice.root");
e6dd99fc 45AliMUONDigitizerv1* dMUON = new AliMUONDigitizerv1(manager)
2058bf30 46manager->AddDigitizer(dMUON);
47manager->Exec("deb");
88cb7938 48
49============================================================
50 How to run MUON RecPoint clusterization
51============================================================
52aliroot -b << EOF
278a86d5 53.includepath $ALICE_ROOT/STEER
54.includepath $ALICE_ROOT/MUON
55.L $ALICE_ROOT/MUON/MUONrawclusters.C++
bf17dbfd 56MUONrawclusters("galice.root",0,9999);
57to Load
58gSystem->Load("$ALICE_ROOT/MUON/MUONrawclusters_C.so")
88cb7938 59
88cb7938 60============================================================
61 How to run MUON Trigger
62============================================================
ba9436c6 63.includepath $ALICE_ROOT/STEER
64.includepath $ALICE_ROOT/MUON
65.L $ALICE_ROOT/MUON/MUONtrigger.C++
bf17dbfd 66MUONtrigger("galice.root",0,9999);
50837721 67To Load
68gSystem->Load("$ALICE_ROOT/MUON/MUONtrigger_C.so")
88cb7938 69============================================================
dcd2690d 70 How to run MUON Tracking reconstruction (old output)
fb76e306 71===========================================================
2058bf30 72.includepath $ALICE_ROOT/STEER
73.includepath $ALICE_ROOT/MUON
74.L $ALICE_ROOT/MUON/MUONrecoNtuple.C++
50837721 75MUONrecoNtuple(0,9999,0,"galice.root")
76To Load
77gSystem->Load("$ALICE_ROOT/MUON/MUONrecoNtuple_C.so")
88cb7938 78First event and last event are given by hand, but this will change.
79
dcd2690d 80===========================================================
81 How to run MUON Tracking reconstruction (new output)
82===========================================================
83.includepath $ALICE_ROOT/STEER
84.includepath $ALICE_ROOT/MUON
85.L $ALICE_ROOT/MUON/MUONTracker.C++
bf17dbfd 86MUONTracker("galice.root",0,9999);
50837721 87To Load
88gSystem->Load("$ALICE_ROOT/MUON/MUONTracker_C.so")
dcd2690d 89Output in MUON.Tracks.root using the new IO
90as a TClonesArray of AliMUONTrack
91
374ebd7d 92Note1.In the actual version (dec-03) the following data
93members of ALiMUONTrack: fgFitter, fEventReconstructor,
94and fTrackHitsPtr are not saved in the MUON.Track.root file
95
88cb7938 96============================================================
97 How to run MUONCheck macro
98============================================================
99To check the content of a root data file, the MUONCheck
100provides a ascii output on screen.
101
102To compile MUONCheck.C
2058bf30 103.includepath $ALICE_ROOT/STEER
104.includepath $ALICE_ROOT/MUON
105.L $ALICE_ROOT/MUON/MUONCheck.C++
bf17dbfd 106To Load
107gSystem->Load("$ALICE_ROOT/MUON/MUONCheck_C.so")
2058bf30 108
278a86d5 109To print Kine : (default file is galice.root )
110MUONkine()
88cb7938 111
112To print hits : (default file is galice.root if not MUONhits("toto.root""); )
2058bf30 113MUONhits()
88cb7938 114
115To print digits : (default file is galice.root)
2058bf30 116MUONdigits()
88cb7938 117
118To print rawcluster : (default file is galice.root)
2058bf30 119MUONrecpoints()
88cb7938 120
121To print trigger : (default file is galice.root)
2058bf30 122MUONTestTrigger()
88cb7938 123
02d8f072 124
125============================================================
126 How to check the Geometry
127============================================================
128gAlice->Init("$ALICE_ROOT/MUON/Config_MUON_test.C");
129.L $ALICE/geant3/TGeant3/G3GUI.C
130G3GUI()
131
132
7985603c 133============================================================
134 How to run MUONdisplay
135============================================================
1eccde20 136First you need to perform a full simulation:
7985603c 137generation, digitalisation and clusterisation
138.L $ALICE_ROOT/MUON/MUONdisplay.C
139MUONdisplay(0,"galice.root")
140
02d8f072 141============================================================
142 Tracking parameters, cuts, energy loss and physics processes
143============================================================
144Tracking parameters in MUON are automatically defined by GEANT
145MUON takes the default values of CUTs and physics processes
146defined by the Config files, except for the gas mixture medium
147of the tracking chambers. The CUT's and physics processes of
148the gas mixture medium is then defined in the galice.cuts file
149in the data directory. In particular ILOSS parameter MUST be
150equal unity (1) in order simulate a realistic energy loss
151distribution (mean value and fluctuations) in the active gas.
a88eb0d0 152
153============================================================
154 Tracking of particle in the magnetic field
155============================================================
156GEANT has two ways for tracking charged particles in the
157magnetic field: HELIX et RKUTA.
158HELIX is faster and works well if the gradient of magnetic
159field is small.
160For MUON, HELIX is a not a good approximation and we must
161use RKUTA to get the optimal mass resolution of the
162spectrometer. The choice of HELIX or RKUTA is done in the
163config file when the magnetic field is defined:
164 AliMagFMaps* field = new AliMagFMaps("Maps","Maps", TRACKING, FACTOR, MAXB, AliMagFMaps::k4kG);
165 gAlice->SetField(field);
166TRACKING must be 1 for RKUTA and 2 for HELIX (the default value for aliroot is 2 (HELIX))
167FACTOR allows you to set the magnetic field to 0, just putting FACTOR=0. Default value is 1.
168MAXB is the maximum magnetic field which is 10.T
169
88cb7938 170===========================================================
171 Still working ..............
172===========================================================