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.
mkrzewic [Thu, 27 Nov 2014 15:41:58 +0000 (16:41 +0100)]
first version of a bash utilities lib
functions used in the runQA.sh and benchmark.sh are put in.
functionality includes robust extraction of run data (run number, data
type, year, etc....)
also some provisions for "clean" bash programming like the parseConfig()
function, which makes it possible to use named parameters to
scripts/functions.
mfasel [Thu, 27 Nov 2014 09:57:08 +0000 (10:57 +0100)]
Change of logic in main trigger selection:
=============================================================
1) High and low threshold triggers are grouped, only the largest of the 2 is selected
2) Main triggers are not cached any more due to this
3) Trigger patch selection in AliAnalysisTaskEmcal reverted to the status before
4) Simple offline triggers are included in the main trigger patch selection
5) Trigger patches are prepared for the simple offline trigger for Gamma patches
mfasel [Wed, 26 Nov 2014 17:14:04 +0000 (18:14 +0100)]
Add task writing EMCAL trigger information into a tree
===================================================================
1) Add Task creating the EMCAL trigger tree
2) Include the new task into the build
3) Add corresponding add macro
mfasel [Wed, 26 Nov 2014 13:26:14 +0000 (14:26 +0100)]
Correct handling of main trigger for multiple trigger classes
==================================================================
1) Modify trigger maker in the way that one can select which type to process (by default all on)
2) Move main trigger patch variable in AliAnalysisTaskEmcal from Pointer to Array (with size of trigger classes)
3) Add argument to the function GetMainTriggerPatch, which is a bitmap, out of which trigger classes to select the main trigger patch
4) If more than 1 trigger class is selected, we choose the highest according to the ADC
5) Consequently enum TriggerType moves from Integer to bits, and the existing part of the code is adapted
gconesab [Tue, 25 Nov 2014 09:39:26 +0000 (10:39 +0100)]
Place the rejection of dead channels in the proper location, currently it can produce many channels rejection if a dead channel is declared because the index to check the next SDigit is not updated
zconesa [Mon, 24 Nov 2014 21:13:13 +0000 (22:13 +0100)]
Updates: (1)added the check on the z coordinate of MC vertex, (2) requirement to have only 2 Lc daughters to reject decays in three prongs in the CF, (3) update the definition of TMVA cuts (A.Alici, C.Zampolli)
ppillot [Mon, 24 Nov 2014 16:44:34 +0000 (17:44 +0100)]
new version to compute trk eff from output of AliAnalysisTaskMuonTrackingEff
- Compute efficiency at DE, chamber, station and spectro levels vs various variables
- 2 options for error calculation: using frequentist or bayesian method
- improve error propagation at station and spectro levels
- integrate efficiency and error over run (if run-by-run weights provided)