Updates in the PHOS/EMCAL raw-data reading code due to the new mapping is PHOS (Yuri). Can't really verify all the changes, but they were tested for PHOS and Gustavo accepted them for EMCAL.
Adding TOF visualization for online display (raw data + clusters). The macros work perfectly well except one simple fix in the clusters (unloading was needed).
new option introduced to ignore the HLTOUT data blocks of the HLT raw data
option 'ignore-hltout' can be set as additional option for the HLT with
AliReconstruction::SetOption, or AliHLTReconstructor::Init respectively
This is in particular useful for HLT chains running on raw data during
AliReconstruction. The output of such chains is added to the HLTOUT collection
and might so interfere with the data produced in the online system and
present in the raw data.
initializing the trigger data structure correctly before component data processing
this was not necessary in AliHLTSystem until now since no component was using the
trigger information so far. Trigger components acces the structure to get information
about CTP trigger classes. The CTP information is not filled yet though, this will be
done in accordance to the trigger framework currently developed for AliSimulation.
filling the event creation time in the EventData struct before invoking component data processing
required to set the ESD timestamp also when running in AliSimulation/Reconstruction
New method to clone current raw-data event and create a single-event raw-reader. Will be used in online display/reco. Not implemented for AliRawReaderFile and AliRawReaderMemory.
cleaning up AliHLTRunStatistics class to be used as a container for run statistics information
copy contructor and assignment operator implemented, TObject::Print, Clone and Clear implemented
1. bug fix: skip the final transport of tracks to the inner TPC X, when the tracks are horisontal
2. few tuning parameters are added
3. compilation warnings fixed
Extra parameters added
--Thi line, and those below, will be ignored--
M HLT/TPCLib/tracking-ca/AliHLTTPCCAStandaloneFramework.cxx
M HLT/TPCLib/tracking-ca/AliHLTTPCCAGlobalMergerComponent.h
M HLT/TPCLib/tracking-ca/AliHLTTPCCATrackerComponent.cxx
M HLT/TPCLib/tracking-ca/AliHLTTPCCAMerger.cxx
M HLT/TPCLib/tracking-ca/AliTPCtrackerCA.cxx
M HLT/TPCLib/tracking-ca/AliHLTTPCCAParam.h
M HLT/TPCLib/tracking-ca/AliHLTTPCCASliceData.cxx
M HLT/TPCLib/tracking-ca/AliHLTTPCCATracker.cxx
M HLT/TPCLib/tracking-ca/AliHLTTPCCADisplay.cxx
M HLT/TPCLib/tracking-ca/AliHLTTPCCAMerger.h
M HLT/TPCLib/tracking-ca/AliHLTTPCCADisplay.h
M HLT/TPCLib/tracking-ca/AliHLTTPCCANeighboursFinder.cxx
M HLT/TPCLib/tracking-ca/AliHLTTPCCAParam.cxx
M HLT/TPCLib/tracking-ca/AliHLTTPCCAGlobalMergerComponent.cxx
M HLT/TPCLib/tracking-ca/AliHLTTPCCATrackerComponent.h
adding AliHLTComponent base class methods to access event properties orbit,
period, bc, and timestamp
GlobalESDConverter initializes ESD header from the event properties
* AliHLTHOMERBlockDesc holds now a copy of the data
* Introduced a buffer to save the last $BUFFERSIZE events
* Added navigation throught the buffer
* Updated the HLT logo
New method to resolve the TRefs and clone the raw-data itself. Will be used in order to clone the raw-data event while creating a single-event raw-reader within the online display/reco. For the moment it seems the best method to do the job. However it will not work in case of two processes (alieve + aliroot) and exchange of event data via sockets. The reason is that the fRawData is non-persistent member of AliRawEquipmentV2.
Allow opening of the file from two places in case at least one of them is read-only. Should not affect any normal offline processing, but unavoidable for online threaded alieve+aliroot reconstruction.
Enabled reading from the MC particles in the AOD, activate with SetReadAODMC(1) (all) or (2) (charged). if activated reconstructed tracks are ignored when FillMomentumArray is called
1. in AliMixedEvent, the method GetMagneticField() returns -999. Is it possible to have, instead, the magnetic field of the first
event used to build the mixed event?
2. in AliMixedEvent, there are 2 methods to get the primary vertex: one is GetPrimaryVertex and returns a null pointer, the second
is GetPrimaryVtx and returns the mean vertex. Would it be possible to remove the second one and let the first one return the mean
vertex?
Yes to 1 and 2
1. Leading time was not decoded properly (there are coarse and fine gains in the HPTDC which I did not not about). 2. HPTDC were written in raw data from 7 to 0 within a ring whereas for everything else it was from 0 to 7. This was Yannick's mistake but he did not want to change the programming of his FPGAs so I had to change it in aliroot. 3. All the ADCs in Float_t instead of integers. (Brigitter). Changes in the ESD classes were agreed by Andreas, Rene confirmed that the schema evolution will handle them properly.
AliCaloTrackAODReader: When requested, keep the selected Tracks and CaloClusters in the output AOD.
AliAnaPartCorrMaker: Do not abort when there is no input analysis, just print that it is doing no analysis.
Added access to magnetic field value in readers. Corrected bugs in AliMCAnalysisUtils when tagging electrons. General updates in AliAnaElectron (Jenn)
Few minor coding violations corrected.
Change in the monitoring policy. Use the DATE monitoring feature which takes events from all GDCs associated to a given run. The run is transmitted via env variable. The GRP preprocessor is changed so that still to give the GDCs, but this time the full list used in the run. This could be useful in the future.
Moving a some structs and classes used for handling "AliESDCaloCluster like" clusters inside HLT.
This was done to avoid dependencies between libAliHLTGlobal and libAliHLTPHOS when we merge
PHOS clusters into the global HLT ESD.
Several classes in the HLT/PHOS had to be changed due to name changes of the structs/classes
- AliMUONQAChecker prevent the method AliMUONQAChecker::CheckRaws to return a NULL pointer if a
TrackerData object is not present in the first specie (kDefault). Now it returns
NULL only if there no TrackerData object at all.
- AliMUONCalibrationData : add a bypass to force the usage of some external calibration data (for AMORE)
- AliMUONTrackerDataWrapper : remove an uneeded method
(Guillaume)
- AliMUONQADataMakerRec : introducing the beautifier for presenting a nicer Raw Data QA to the shifter.
This is just a first approach, as most of that should probably be done in the Checker on the longer term (to be discussed...)
- AliMUONDigitCalibrator & AliMUONTrackerDataMaker : do not force the number of sigma to cut on the charge. Should be taken from the recoparam.
This was impacting the QA only (forcing it to use a 3 sigma cut, where anywhere else we use 4 sigma cut).