EmCal Data Manager

The required accuracy demanded by the physics program of PHENIX/EMCAL can only be achieved by a careful calibration and survey of the detector. Thus the online EMCAL group has put a great effort on developing a set of software packages devoted to make the online calibration and to detect potential hardware or software failures. The Data Manager (DM) is one of these packages. It is acting as a central manager for the data that must be put in (and read from) DataBase. The basic idea is that every and each part of EmCal software that wants to access the DB uses the DM. The DM is offering a uniform interface to the DB, regarless of the kind of data you want to store/retrieve from it. The "low" level access to the actual DB is using the pdbcal framework of the PHENIX Offline group.

A basic introduction of the DM principles has been made at the EmCal meeting on 22-Dec-1999. Principles have not evolved much since then, but the code has ! See below for links about the code and its documentation.

Code and documentation

The Data Manager work is split in two modules. Both are primarely part of the CVS online/monitoring/emc/Common hierarchy (they are also from time to time "mirrored" to /offline/packages/emc-calib repository to be used by the reconstruction chain).

• The DataManager package defines the base classes of data management.
• The DataManager_plugins package defines some plugins (for the moment, there are 3 of them which can handle Gain, Pedestal and HLRatio objects).

You can also browse:

• The latest DOC++ documentation of the code (DataManager and also other related packages).
• Full doc. about calibration and databases[HTML] [PS]

Some very early discussion on EmCal DB (outdated, but might still be readable...)

• Where do we stand with the DB issue ? A short status report.
• First step to get a global design : use cases.
• Transparencies for the Nov 9 video-conference : PPT or PS.