nick [Mon, 25 Jun 2007 09:35:08 +0000 (09:35 +0000)]
25-jun-2007 NvE Warning messages suppressed in the IceMakeHits processor to prevent
TSpectrum warnings in case of (noisy) waveforms with very many peaks.
nick [Sun, 24 Jun 2007 12:05:05 +0000 (12:05 +0000)]
23-jun-2007 NvE Support for locking introduced in AliAttrib and locked signal (and error)
treatment implemented in SetSignal() and SetSignalError() of AliSignal.
Also the AliSignal copy constructor has been updated for the new locking.
24-jun-2007 NvE Treatment of TWRDaq data introduced in IceCleanHits.
07-jun-2007 GdV OM readout type also updated from the data contents in IceRoot.cxx.
08-jun-2007 GdV Support introduced in IceRoot.cxx to set the waveform binsize based on the
info from the data of the I3 file.
08-jun-2007 NvE First attempt for TWR ADC calibration in IceCal2Root.cxx.
09-jun-2007 GdV OM 681 now also ignored in IceRoot.cxx.
21-jun-2007 GdV Trigger device and "main" trigger introduced IceRoot.cxx to provide
the actual trigger time(s).
21-jun-2007 NvE External stop and (first) trigger time taken into account for the
TWR waveform timebins in IceRawTWR. This will provide a better
synchronisation of the various waveforms and consequently of the
extracted LE values.
23-jun-2007 NvE Creation of OM slotnames "THRESH", "SENSIT" and "READOUT" deactivated in
IceCal2Root since these values are currently not known from the available
ascii database files. Furthermore, "READOUT" and "THRESH" are provided
in the TWR (raw) data themselves and having them as empty database entries
resulted in overwriting of the (raw) data values by the empty dbase ones.
In case in the future one wants to provide default dbase values, which
might be overwritten by values from the data themselves, on should "lock"
the signal values from the data using the newly introduced locking facility
of AliAttrib and AliSignal.
Also all slots in IceCal2Root now created via the "AddSlotName" facility
and slot access exclusively via the slotname, to enhance flexibility.
nick [Thu, 21 Jun 2007 14:35:10 +0000 (14:35 +0000)]
07-jun-2007 NvE Maximum OM id changed from 681 to 680 in IceRawTWR.cxx to ignore the signals
of OM 681 which is always regarded is being bad.
Also new OM slotname "READOUT" introduced in IceCal2Root, IceF2k and IceRawTWR
to identify electrical, optical and digital readout based on the Dbase info
and/or actual settings in the various data files (headers).
07-jun-2007 GdV OM readout type also updated from the data contents in IceRoot.cxx.
08-jun-2007 GdV Support introduced in IceRoot.cxx to set the waveform binsize based on the
info from the data of the I3 file.
08-jun-2007 NvE First attempt for TWR ADC calibration in IceCal2Root.cxx.
09-jun-2007 GdV OM 681 now also ignored in IceRoot.cxx.
21-jun-2007 GdV Trigger device and "main" trigger introduced IceRoot.cxx to provide
the actual trigger time(s).
21-jun-2007 NvE External stop and (first) trigger time taken into account for the
TWR waveform timebins in IceRawTWR. This will provide a better
synchronisation of the various waveforms and consequently of the
extracted LE values.
cvetan [Wed, 20 Jun 2007 10:58:40 +0000 (10:58 +0000)]
Improved version of the ALICE geometry manager. The main improvements are: a) LUT with original (ideal geometry) matrixes for all the sensistive volumes. The LUT is initialized before misaligning the geometry; b) New method LoadGeometry() which can be used to load the geometry either from CDB (default case) or from user-defined geometry.root file; c) The Instance() method has been removed and all the public methods become static. All the access to the geometry is done via pointer to the loaded TGeoManager insted of gGeoManager. This should allow, for example, AliEVE to load several geometries in one session.
cvetan [Wed, 20 Jun 2007 10:50:05 +0000 (10:50 +0000)]
Improving the time performance of the TPC clusterer. The idea is to use an auxiliary array containing the indeces of the timebins with signal above the threshold. The overall speed-up factor in case of zero-suppressed raw-data reconstruction is about 2 to 3. In case of digits reconstruction the gain is about 2. In case of pedestal calculation and subtraction on the flight the gain is expected to be minor or at least the should be no significant performance penalty.