gconesab [Tue, 10 Nov 2009 18:13:34 +0000 (18:13 +0000)]
--- Access to bad channel map implemented in reconstruction chain.
-A first method to calculate the distance from a cluster to closest bad channel implemented.
Output kept in AliESDCaloClusters::GetDistanceToBadChannel
-Ideal map (no dead channels) committed to OCDB/EMCAL/Calib/Pedestals
Example macro to create a bad channel map to be put in OCDB is in EMCAL/macros/PedestalDB
abercuci [Tue, 10 Nov 2009 08:13:11 +0000 (08:13 +0000)]
switched from treating all layers independently to a gegenral
training for all layers. A first look at the performance shows that it
seems to be ok (AlexW)
richterm [Mon, 9 Nov 2009 23:41:13 +0000 (23:41 +0000)]
putting back the old definition of Run
int Run(Int_t iNofEvents=1, int bStop=1)
because there have been problems on mac with the 64 bit variable and its default variable in the extended argument list
int Run(Int_t iNofEvents=1, int bStop=1, AliHLTUInt64_t trgMask=0);
The old function now forwards to the new function with 0 for the trigger mask. The function is defined without default arguments.
mtadel [Mon, 9 Nov 2009 17:32:06 +0000 (17:32 +0000)]
* esd_tracks.C
Add function esd_tracks_by_anal_cuts(). It takes cuts created by
PWG0/CreateStandardCuts.C and puts tracks into two categories:
accepted / rejected.
Remove global g_esd_tracks_by_category_container -- no longer used
for track counting.
* visscan_init.C
Add AliEveMacro for esd_tracks_by_anal_cuts().
* alieve_main.cxx
Use projectable-compound selection mode.
Unmap main EVE window before entering TEveManager::Terminate().
ivana [Mon, 9 Nov 2009 16:37:07 +0000 (16:37 +0000)]
Taking into account the time information of the hit in the digitization
- done in AliMUONSDigitizerV2, still to be done in AliMUONDigitizerV3.
(Mercedes)
aszostak [Sun, 8 Nov 2009 22:21:19 +0000 (22:21 +0000)]
Fixing bug related to incorrect unloading of shared library and class code.
This is related to:
https://savannah.cern.ch/bugs/?58083
https://savannah.cern.ch/bugs/?58247
In actual fact this is a workaround for the bug/feature/limitation (whatever you want to call it) in ROOT/CINT that removes more libraries than just the one that was
requested to be removed. The problem has been solved by adding more protection to prevent the segfault, printing of appropriate warnings and cleaning up HLT components in
the correct order to prevent the problem in the first place.
marian [Sun, 8 Nov 2009 16:47:23 +0000 (16:47 +0000)]
Adding alarms and graphical representation of alarms
(Jens)
AliTPCcalibDB.cxx.diff Add loading of dataQA, adopt creation of GUI tree
AliTPCcalibDB.h.diff Add loading of dataQA, adopt creation of GUI tree
AliTPCcalibDButil.cxx.diff Add loading of reference data, creation of reference GUI tree
AliTPCcalibDButil.h.diff Add loading of reference data, creation of reference GUI tree
AliTPCCalibViewerGUI.h.diff Add getters to handle custom draw strings
AliTPCCalibViewerGUItime.cxx.diff Add getters to handle custom draw stings. Code cleanup.
AliTPCCalibViewerGUItime.h.diff Adopt gui tree / reference tree creation / loading
AliTPCMonitor.cxx.diff For root raw files add possibility to navigate to a certain event in the file
libTPCbase.pkg.diff Add AliTPCCalibQAChecker, AliTPCCalibViewerGUIAlarms
TPCbaseLinkDef.h.diff Add AliTPCCalibQAChecker, AliTPCCalibViewerGUIAlarms
AliTPCCalibQAChecker.cxx New class for calib data checking, mostly based on tree draw, but also histograms, graphs, numbers
AliTPCCalibQAChecker.h New class for calib data checking, mostly based on tree draw, but also histograms, graphs, numbers
AliTPCCalibViewerGUIAlarms.cxx New class. GUI interface for calibration alarms. Will be used in AMORE and offline.
AliTPCCalibViewerGUIAlarms.h New class. GUI interface for calibration alarms. Will be used in AMORE and offline.
richterm [Sun, 8 Nov 2009 12:07:59 +0000 (12:07 +0000)]
allow names with the '-' character in items. This is a temporary solution like in r35411.
It has beendeactivated in r36097, but it turns out to be necessary again for the correct
evaluation of the trigger menu until the final concept is in place
See https://savannah.cern.ch/bugs/index.php?58205
richterm [Sat, 7 Nov 2009 23:32:33 +0000 (23:32 +0000)]
removing all code regarding the solenoidBz OCDB entry formerly used
to propagate the field value from DCS to the components in the online
system. The framework now initializes the global AliMagF instance,
which is used by the components fot the field setup
richterm [Sat, 7 Nov 2009 22:41:00 +0000 (22:41 +0000)]
adding documentation of the field conventions
using the AliGRPManager again for verbose output
changing the default polarities (corresponding to positive fields):
l3: positive -> 0
dp: negative -> 1