\section sim_s3 Tracking of particle in the magnetic field
-GEANT has two ways for tracking charged particles in the
+GEANT has two integration methods for tracking charged particles in the
magnetic field: HELIX et RKUTA.
HELIX is faster and works well if the gradient of magnetic
field is small.
spectrometer. The choice of HELIX or RKUTA is done in the
config file when the magnetic field is defined:
<pre>
- AliMagFMaps* field = new AliMagFMaps("Maps","Maps", TRACKING, FACTOR, MAXB, AliMagFMaps::k5kG);
- gAlice->SetField(field);
+ TGeoGlobalMagField::Instance()
+ ->SetField(new AliMagF("Maps","Maps", INTEG, FACTOR_SOL, FACTOR_DIP, MAXB, AliMagF::k5kG));
</pre>
-TRACKING must be 1 for RKUTA and 2 for HELIX (the default value for aliroot is 2 (HELIX))
-FACTOR allows you to set the magnetic field to 0, just putting FACTOR=0. Default value is 1.
-MAXB is the maximum magnetic field which is 10.T
+INTEG must be 1 for RKUTA and 2 for HELIX (the default value for aliroot is 2 (HELIX)).
+FACTOR_SOL, FACTOR_DIP allow you to set the multiplicative factor for solenoid
+and dipole, respectively; just putting FACTOR_SOL=0 or FACTOR_DIP=0 will set the
+magnetic field for solenoid or dipole to 0. Default values are 1.0, 1.0.
+MAXB is the maximum magnetic field which default value is 10.T
-\section sim_s4 MUON cocktail generator
+\section sim_s4 Tailing effect
+
+The control to turn on/off the parametrized tailing effect:
+<pre>
+AliMUON::SetTailEffect(Bool_t),
+</pre>
+
+The parameter to tune increase/decrease the tailing effect is kept inside,
+AliMUONResponseV0::DisIntegrate(). This parameter is an integer number
+(excluding zero and four), the higher the value is the less is the tailing
+effect:
+<pre>
+Int_t para = 5;
+</pre>
+Zero is excluded because it gives straight line transformation, and four
+is excluded because the AliRoot simulation chain spends VERY VERY long
+time in AliMUONResponseV0::DisIntegrate method, which reason was not yet
+understood. The parameter for 1, 2, 3, 5, 6, 7, 8, 9, 10 were checked with
+no slowing down problem, however parameters greater than 6 give almost no
+tailing effect since they basically correspond to higher order polynomial
+transform.
+
+
+\section sim_s5 MUON cocktail generator
There is a MUON cocktail generator of the muon sources in the
EVGEN directory. This class derives from AliGenCocktail.
gener->Init();
</pre>
-\section sim_s5 How to simulate events with misaligned geometry in local CDB
+\section sim_s6 How to simulate events with misaligned geometry in local CDB
If you want to use a misaligned geometry to simulate some
events you can use a local CDB. For this need to follow
<pre>
aliroot -b >& testSim.out << EOF
AliCDBManager* man = AliCDBManager::Instance();
-man->SetDefaultStorage("local://$ALICE_ROOT");
+man->SetDefaultStorage("local://$ALICE_ROOT/OCDB");
man->SetSpecificStorage("MUON/align/Data","local://ResMisAlignCDB");
AliSimulation MuonSim("$ALICE_ROOT/MUON/Config.C");
MuonSim.SetWriteRawData("MUON");
EOF
</pre>
-\section sim_s6 How to Merge events
+\section sim_s7 How to Merge events
You can merge 2 types of simulated events. For example,
you can simulate Hijing events, and then simulate muons
EOF
</pre>
-\section sim_s7 On track numbering
+\section sim_s8 On track numbering
All generated particles, including primary and secondary
particles are put on the stack. The secondary particles are kept