gconesab [Wed, 3 Dec 2014 17:18:54 +0000 (18:18 +0100)]
AOD particles with cluster index 0 were not checked for their shower shape, avoid the check on the cluster index and do the shower shape cut only when the range is defined
cholm [Wed, 3 Dec 2014 11:15:39 +0000 (12:15 +0100)]
Handle deletion of AliFMDAltroMapping object. If we make the object
ourselves, make sure to set the bit TObject::kCanDelete. If the
object comes from OCDB, make sure to clear that bit. Only delete the
object if TObject::kCanDelete is set.
Note, AliFMDAltroMapping is a static object. None of it members
ever various based on run number or the like. It reflects the
static nature of the hardware mapping of the FMD.
fbock [Tue, 2 Dec 2014 11:31:44 +0000 (12:31 +0100)]
- changed cut selections for all calo related tasks, changed definition of cuts for min energy, and definition of phi cuts to follow ALICE convention reaching from 0-2Pi
fbellini [Mon, 1 Dec 2014 16:53:47 +0000 (17:53 +0100)]
Updates of trending macro for QA outputs from AliAnalysisTaskTOFqa:
- cleanup of commented lines
- added PIDqa output with subtracted start time
- increased protection for non-available plots (eg. older aliroot versions)
- fixed canvasE flag
cholm [Mon, 1 Dec 2014 10:10:09 +0000 (11:10 +0100)]
Various small fixes:
- Correct polarity for pA/Ap collision w/DPMJet
- Add possiblity to do Fast simulation (generator only) using
the configurations here. The simulation is implemented as a
TSelector which allows us to execute the fast simulation in
Proof(Lite) for better performance. The script RunFast.C takes
care or running the simulation given simple arguments:
- Proof or not proof
- Run number to 'anchor' in - really this is only used to look
up the relevant beam parameters from OCDB/GRP
- Optional impact parameter range
- Optional Event generator to use
- How often to get back monitor histograms (or not at all)
- Initial go at a VirtualTrain class for QA and AOD (not used)
- Clean up library loading in BaseConfig.C
zconesa [Sun, 30 Nov 2014 19:54:02 +0000 (20:54 +0100)]
(1) Fix of the cross section calculation bin width with no feed-down correction. (2) Optimize the calculation of pt bining to happen only at initialization.
mfasel [Fri, 28 Nov 2014 16:48:27 +0000 (17:48 +0100)]
Decouple trigger maker completely from AliEMCALTriggerTypes.h
=============================================================
1) Trigger patch gets as offset 0 by default, it has to be specified
explicitly by the trigger maker
2) Remove includes of the header file in the trigger maker and the
trigger patch
shahoian [Fri, 28 Nov 2014 16:03:19 +0000 (17:03 +0100)]
Extended AliESDtrackCuts::GetReferenceMultiplicity(..,etaRange) to (..,etaRange,etaCent=0) to allow estimates in asymmetric ranges etaCent-etaRange : etaCent+etaRange
mfasel [Fri, 28 Nov 2014 13:51:58 +0000 (14:51 +0100)]
Allow usage of old bit configuration via the add macros
===============================================================
By default the new bit configuration is used, however users can switch
on the new old configuration via the add macro
(AddTaskEmcalTriggerMaker.C and AddTaskJetPreparation.C). The parameter
is placed at second but last position keeping the one for the trigger
patch QA as the last one.
mfasel [Fri, 28 Nov 2014 13:25:51 +0000 (14:25 +0100)]
Adapt trigger patch maker to different bit settings:
============================================================
It turned out that the number of trigger bits used in different aliroot
versions is different (old aliroot - no distinction between high and low
threshold triggers). Therefore the usage of the trigger bits defined in
AliEmcalTriggerTypes.h leads to incorrect trigger patches when using it
for samples producecd with old aliroot versions. In order to overcome
the problem, the enum with hard coded trigger bits is removed from the
trigger maker and the trigger patches, and replaced by a class storing a
trigger bit configuration, which can be adapted to the conditions of the
sample to be analysed. The fix also fixes a bug introduced by a naming
clash for the Level0 trigger bit.