marian [Wed, 4 Feb 2009 18:44:00 +0000 (18:44 +0000)]
AliTPCLaserTrack.cxx.diff Add absolute laser track ray length from the last common point (needed for exact drift velocity calculation), gene
ral updates
AliTPCLaserTrack.h.diff Add absolute laser track ray length from the last common point (needed for exact drift velocity calculation), gene
ral updates
morsch [Wed, 4 Feb 2009 15:32:53 +0000 (15:32 +0000)]
Some little changes in AliDecayerPythia::ForceHadronicD, in
order to force the following decay channels:
1. Lambda_c --> Lambda pi
2. Lambda_c --> Lambda(1520) pi (resonant for Lambda_c --> pKpi)
3. D0 --> K*0 pi pi (resonant for D0 --> 4 prongs)
(Rossella Romita <r.romita@gsi.de>)
prino [Wed, 4 Feb 2009 15:15:02 +0000 (15:15 +0000)]
Modifications to ITS standalone tracker: 1) improve efficiency at low pt for p-p 2) remove unwanted eta cut 3) possibility to reject noise clusters in SDD and SSD with a cut on cluster charge (F. Prino)
ivana [Wed, 4 Feb 2009 13:29:49 +0000 (13:29 +0000)]
Changes in trigger:
- Add initialization of Apt histograms in AliMUONTriggerLut (otherwise they
are "null" when created via AliMUONTriggerIO, eventhough they are not used
anymore)
- Modify the Compare function in AliMUONTriggerLut in oder to properly loop
over the TH3 bins
- Change destinations of GLOBAl and REGIONAL trigger configuration CDB files
in the AliMUONTriggerSubprocessor (the old destinations were not used, anyway,
when the calibration data was initialized) to the same locations were
identical objects are written by AliMUONCDB; remove old destinations in the
CDB (?)
- Add a new ROOT file for the trigger Look-Up-Table with all-pt and low-pt
cuts (the old one contains low-pt and high-pt cuts) to be used when the CDB
entry is created by hand using AliMUONCDB
- Update READMEtrigger with an explanation of the two LUT ROOT files
(Bogdan)
ivana [Wed, 4 Feb 2009 12:10:48 +0000 (12:10 +0000)]
In mapping:
Moving kStation1 and kStation2 from AliMp::StationType;
(there is kept only one value for stations 1 and 2:
kStation12) into a new enum, AliMq::Station12Type.
This should prevent from eventual mixing of these
values with the new value kStation12, representing sector
stations type (analogue to kStation345).
cvetan [Tue, 3 Feb 2009 21:27:36 +0000 (21:27 +0000)]
Moving the OCDB object and mag field from the selector's input list to the input-data file in PROOF. Tested with v4-16-Release and root 5-22-00 on CAF. The PROOF based reconstruction would need further fixes in the trunk to accomodate for the new mag field related changes in root and aliroot.
hdalsgaa [Tue, 3 Feb 2009 11:15:12 +0000 (11:15 +0000)]
This is rather large upgrade of the analysis. The sharing correction has been improved, the particle cut moved to AliFMDAnalysisTaskDensity. Reading of MC data for comparison has been implemented in AliFMDAnalysisTaskDndeta and the scripts to run the analysis
fca [Sun, 1 Feb 2009 11:42:22 +0000 (11:42 +0000)]
The present commit corresponds to an important change in the way the
Magnetic qField is used in AliRoot.
- Only one field will be supported, the Chebichev parametrisation
developed by R.Shahoyan, with the name AliMagF. Different field
strengths will be obtained by changing the scale factor for the
dipole and the solenoid fields. Some highlights of these changes are
here
- All other mag field classes and maps are deleted
- The field is accessed via a call to
TGeoGlobalMagField::Instance()->Field(...) both in simulation and in
reconstruction. This has involved changes in very many files in the
following modules: ACORDE, BCM, EMCAL, EVE, FMD, HLT, HMPID, ITS,
MONITOR, MUON, PHOS, PMD, PWG1, PWG3, RAW, STEER, STRUCT, T0, TOF,
TPC, TRD, VZERO, ZDC, test.
- The modifications to account for the new field were done in the
compilable code and in all the macro. These have now to be carefully
tested by the authors.
- If your macros are creating the field, note that the field should be
constructed as:
AliMagF* fld = new AliMagF(
const char *anyname, // same as before, up to you
const char* anytitle, // same as before, ...
Int_t integ, // same as before, geant
Double_t factorSol=1.,// scaling (including the sign) for the solenoid
Double_t factorDip=1.,// new parameter, scaling for dipole
Double_t fmax=15, // same as before
BMap_t maptype = k5kG,// map type: choices are AliMagF::k5kG,
// AliMagF::k2kG and k5kGUniform
// the latter will provide former AliMagFC-like
// field: constant Bz for L3, BX parabolic in
// Z for dipole
const char* path="$(ALICE_ROOT)/data/maps/mfchebKGI_sym.root",
// parameterization file to use.
BeamType_t btype=kBeamTypepp, // used to define the field for ZDC,
// choices are: AliMagF::kBeamTypeAA,
// AliMagF::kBeamTypepp, liMagF::kNoBeamField
Double_t benergy=7000., // currently only 450, 5000 and 7000 are
//supported, will be changed soon
Bool_t compensator=kFALSE // this are compensator dipoles for the
// Muon dipole, most probably it will be
// eliminated soon, set it to kTRUE for
// the moment
);
- Note that in order to make the field available to Aliroot it should
be registered by
TGeoGlobalMagField::Instance()->SetField(fld);
- The following lock will prevent the field from resetting:
TGeoGlobalMagField::Instance()->Lock();
- In the macros and in the code the field may be accessed via either
direct call
or casted to
AliMagF* fld = (AliMagF*)TGeoGlobalMagField::Instance()->GetField();
in case you need the methods like GetTPCInt().
- Since many classes use only Bz component, I've added a new method
AliMagF::GetBz(const double* x) which computes the Bz w/o spending
the time on Bx,By.
morsch [Sun, 1 Feb 2009 10:59:34 +0000 (10:59 +0000)]
AliGenMUONCocktailpp is used with modified values of the
different cross-sections, hidden (as much as possible) from the people
who will analyze afterwards the results, in order to see the accuracy
of the physics analysis when unknown cross sections are at the input of
the Monte-Carlo. By default the hardwired values are used, and only if
intentionally some env variables are defined the values will be
changed, without print-out in the log file (as default).
(Bogdan Vulpescu)
aszostak [Thu, 29 Jan 2009 17:52:56 +0000 (17:52 +0000)]
Adding extra options to the hit reconstructor component to better control recovery from data corruption and skipping of data words with detected parity errors.
Fixing logging messages in AliHLTMUONTriggerReconstructor.
pulvir [Thu, 29 Jan 2009 16:35:13 +0000 (16:35 +0000)]
AliRsnMCInfo:
- added a datamember to store MC first point of track (for MC DCA)
- added all setters/getters related to this
- added a method to "shift" this point by the amount
of a reference point (primary vertex)
AliRsnDaughter:
- in method "PhiDeg" and "ThetaDeg" call their radiants counterparts
(they are inline so the compilation will be the same, but is more readable)
- add user-friendly methods to set the "kink" index accordingly
- explicitly added and "Adopt" for a TParticle object, used also for AliMCParticle
AliRsnEvent:
- added the MonteCarlo primary vertex and getters/setters for it
- added a method to correct trach DCA's for primary vertex which will be possible only from here
AliRsnCut:
- added track cut on MC impact parameter
- added track cut on kink daughter/mother
- corrected typo in cut on transverse momentum MC
- added event cut on Vz primary vertex
- added a method to know if the analyzed pair is made of the same tracks (e.g.: pi+pi+ k+k+ etc)
- added a method to know if the object is being used for mixing
- removed all methods which refer to event buffer and event matching search
- removed management of event mixing which is moved to analysis task
AliRsnPair:
- removed option "kTruePairs" (replaced with true pairs cut)
- removed "mixNum" value in constructor (mixing is managed at level of AnalysisTask object)
- removed unused "Init" method
- changed arguments of "ProcessPair" method to two AliRsnEvent (event buffer is not here any longer)
- removed "mixing cut" and everything referring to it
AliRsnReader:
- moved conversion methods from source to AliRsnDaughter here
- added an AliESDtrackCuts data-member for primary cuts (optionally used) and getters/setters for it
AliRsnAnalysisSE:
- added management of event mixing at the level of this object
AliRsnFunction:
- removed weighted filling of histograms
- added possibility to create bins for many variables (separately)
gconesab [Thu, 29 Jan 2009 10:28:56 +0000 (10:28 +0000)]
1)Terminate() method implemented in the frame. Simple examples on what to do with it put in AliAnaExample and AliAnaPi0
2)New class AliMCAnalysisUtils, extracted method CheckOrigin from AliCaloPID, added some other MC generator utilities
3)Event number can be accessed in the analysis classes with method GetEventNumber
4)AliAnaCaloTrigger derives now from AliAnalysisTaskSE, MC additional information done in AliAnaCaloTriggerMC moved here
aszostak [Wed, 28 Jan 2009 17:26:04 +0000 (17:26 +0000)]
Adding extra protection code to prevent seg-faults when processing online data. (Indra)
Added option to RunChain.C to use the raw reader publisher component rather than just a plain file publisher.
ivana [Wed, 28 Jan 2009 11:07:09 +0000 (11:07 +0000)]
In mapping:
Introduced new methods in AliMpSegmentation class for access
to AliMpSector, AliMpSlat and AliMpTrigger objects,
and replaced code where these objects are accessed via
unsafe casting AliMpVSegmentation with use of these new functions.
(Ivana, Laurent)