General on the Database z Do we want to use the tools developed by Mark to store calibration and geometry values ??? yAre we sure we want to use Objectivity ?? yAre there oppositions or new suggestions ?? zFew (or better no) further development on the base- classes since last meeting (due to several problems to use Objectivity) ythe idea to use Mark’s code as a black box has appeared to be not the most convenient method ysince Mark left a lot of knowledge has been lost, its imperative to have someone who can take his place yan idea could be to generate the PHENIX Objectivity Federation --> maintained by an ‘expert’ (???) F.Messer

Calibration zMark’s tools ‘can’ be used for calibration purposes : ySet the Gain / Drift Velocity / To /etc… for a channelis done using a single (and very general) base class. xA channel is not necessarily a single electronic channel xIt could be a module, a keystone, a chip or whatever you prefer yThe information is then stored in a Bank which collects all the values for a subsystem (or sub-sub system) zValues to be stored are obtained using some kind of stimuli (‘artificial’ or ‘natural’) yFor the DC: Drift Velocity and To could be obtained by the drift time distributions for each channel (utilities : fitting the distribution with an appropriate function need to be furnished by the subsystem)

zTo take care of inefficiency or dead channels (probably needed mostly for the Monte-Carlo) yFlag dead channel yor Set Gain = 0 zAlignment information is probably written ‘somewhere’ in some kind of database. It will need to be accessible in the very near future and stored in THE Database yFor the DC: the alignment info is at the PNPI yBetter geometry calibrations need to be extracted from the data ---> needed No Field Data (with enough statistics) or an appropriate Track Model

The Drift Chamber zGLOBAL : yFor each arm: x Calibration values will be time dependent (Pressure, Temperature, Gas Purity changes) xa Canary Chamber will be used to measure V. Drift and its changes zLOCAL: y For each wire: xDrift Velocity and To for each wire (~ events). the distributions need to fitted and the values stored in the calibration database --> could be done Online once the tools have been developed xDrift Velocity as a function of z (or theta). Dependent on the needed granularity. (for 10cm --> *10 = ) xcalibration of V.drift as function of drift distance could be also needed