Deprecated List

Class dEmcCalibTower
This used to be our storage object for towers in DSTs. New objects are emcTowerContainer/emcTowerContent.

Class dEmcCluster
see emcClusterContainer/emcClusterContent now.

Class dEmcClusterLocal
see emcClusterContainer/emcClusterContent now.

Class dEmcClusterLocalExt
see emcClusterContainer/emcClusterContent now.

Class emcCalibratedDataObject
It derives from PHObject so it can be written in a TTree using the PHNodeIOManager of PHOOL.

Class emcCalibrator
(as soon as online code does not need it anylonger). See emcDataProcessor instead.

Class emcCalibratorFactory
To be depcreated as soon as online code does not use it anylonger, as emcCalibrator class itself is to be deprecated.

Class emcFEMtuple
A FEMtuple is basically a vector of emcCalFEM, and as such is quite easy to implement directly in user code (currently it's only used in the calibrator, a class which will also soon be revisited anyway...). Thus the following documentation might not be really accurate.

Class emcFEMtupleFactory

Class emcGains

Class emcHLRatios

Class emcLCTofs

Class emcMixedDataObject

Class emcObjectFiller
The Object Filler scheme was developped at the time of the "multi-pass" dataproduction (PRDF to DST, DST to microDST, microDST to nanoDST). It never was fully finalized before we switched to Fun4All, and as such might be considered as deprecated, even though I could imagine some use cases for it, still.

Member emcObjectManager::CanCollect (const emcManageable &) const
Can we collect such object ?

Class emcOMFEMtupleT< BM, FT >

Class emcPedestals

Class emcPedestals5

Class emcQAs

Class emcRawDataCalibrator

Class emcRawDataCalibratorV1

Goes from raw data to calibrated data.

Class emcRawDataCalibratorV2

Goes from raw data to calibrated data.

Class emcTacPeds

Class emcTofT0s

Class emcWalkTofs

Class mEmcClusterNewModule
With the removal of the usage of STAF tables, see now mEmcClusterizerv0

Member emcObjectManager::Collect (const emcManageable &, const PHTimeStamp &)
Collect a manageable from the DB. See the DM interface for parameters. Unless allowed explicitely by a particular Object Manager, in general the returned pointer (should not be deleted) by the receiver !

Has been deprecated because handling of collections is better done elsewhere. That's not the job of the datamanager, after all...

Member emcDataManager::Collect (const emcManageable &object, const PHTimeStamp &when)
Collect 1 big manageable valid for all the supermodules in the current configuration.