1) Centrality dependent thresholds parameters
2) The PID method is now an argument in the functions. In the current implementation the PID method is a class member and can be modified by anybody which is
dangerous if many users are interacting.
The user can now select the method in the functions in AliPIDResponse, 1D is chosen by default. These changes require some small changes in the TRD folder and
the tender supply.
3) As a consequence, only for the 1D PID cached values are used and the 2D PID is recalculated (1D is standard method and 2D is only used by some users so far)
Updated macros for D-electron correlation analysis (Matthias):
- support for external macro AddGoodRuns
- bugfix: number of directories for local AOD collection
- setting TTL to 24h
- code cleanup, formatting and documentation
1) bug fix in AddAliEbyEHigherMomentsTaskCentrality.C 2) Replaced GetTPCNcls() with GetTPCClusterInfo(2,1) in AliEbyEHigherMomentsTask.cxx (Nirbhay Kumar Behera <nirbhay.kumar.behera@cern.ch>)
- removed old double-gap analysis task by Xian-Guo Lu
- added new example-analysis task based on the old version, which is intended to be a common basis for future analyses on double-gap events and central diffraction
1) Adding class AliAnalysisMuonUtility which contains static methods allowing to process AOD and ESD (muon) tracks in the same way. Using this class, there is no more need for the user to adapt his/her analysis code to run on AODs or ESDs. 2) Adding AliMuonEventCuts to handle cuts on event (e.g on fired trigger and SPD vertex). It also provides a way to select trigger classes based on their name (useful to fill information on many muon trigger classes at the same time). (Diego)
1) Adding class AliAnalysisMuonUtility which contains static methods allowing to process AOD and ESD (muon) tracks in the same way. Using this class, there is no more need for the user to adapt his/her analysis code to run on AODs or ESDs. 2) Adding AliMuonEventCuts to handle cuts on event (e.g on fired trigger and SPD vertex). It also provides a way to select trigger classes based on their name (useful to fill information on many muon trigger classes at the same time). (Diego)
In AliHFAssociatedTrackCuts:
- possibility to select a specific process for MC analysis (gluon splitting, pair production etc)
- IsMCpartFromHF returns an array of 4 booleans containing infos on track origin (from charm, from beauty, from D meson, from b meson)
- a string is added to store comments in the cut object
In AliHFCorrelator
- added flag to select if perform the analysis on reconstructed tracks or generated particles
- in AcceptAndReduceTracks adde the possibility to save a TObjArray of charged particles in a given pt range/PDG code
In AliAnalysisTaskDStarCorrelations:
- added control histograms for event mixing
- updated methods that calls AliHFAssociatedTrackCuts::IsMCpartFromHF
- added tha analysis with correlation to leading particles
- added possibility to select on event type (for MC)
- bug fix with normalizationcounter
In AliAnalysisTaskSEDplusCorrelations:
- updated to make it compatible with new method AliHFAssociatedTrackCuts::IsMCpartFromHF
Updates in Lambdac->pKpi selection (Rossella)
1. the "soft " Bayesian method is implemented
2. the possibility to check on that the pT of the proton is > pT of the pion is implemented (fUseSpecialCut)
3. the nsigma cut strategy is loosen, i.e. the discarding of the tracks has been removed.
git://git.uio.no / u / mrichter / AliRoot.git / log