ALICE Calibration Requirements
V0 OK July 06
Par # Parameter Data format/size per channel Data size (Total) Bytes Update freq Source Confirmed  Run type / Trigger type # of required events/sampling rate Processing level: sub-event or event Results: FEE/Archive Accessible by offline Calib. Procedure in AliRoot use case #
      on FES in OCDB reference                                                                
1 gains 32 bits (TBC)   512[1] 0 Run DAQ (on line data) * yes physics data * at least 2000 L2 (TBC) event and sub-event DAQ FES / OCDB  yes fall 2006 6
2 pedestal means 32 bits (TBC)   512 0 Run DAQ (on line data) * yes physics data * at least 1000 L2 (TBC) event and sub-event FEE and  DAQ FES / OCDB  yes fall 2006 6
3 pedestal sigmas 32 bits (TBC)   512 0 Run DAQ (on line data) * yes physics data * at least 1000 L2 (TBC) event and sub-event FEE and  DAQ FES / OCDB  yes fall 2006 6
4 time gains 32 bits (TBC)   256[2] 0 Run DAQ (on line data) * yes physics data * at least 10000 L2 (TBC) event DAQ FES / OCDB  yes Unknown 1
5 time offsets 32 bits (TBC)   256 0 Run DAQ (on line data) * yes physics data * at least 10000 L2 (TBC) event possibly FEE and  DAQ FES / OCDB yes Unknown 6
2048 0
* dedicated runs will be used for an initial calibration
DCS access - offline has access only to DCS archive DB, curently no access to configuration DB
DAQ - offline has access to raw data and DAQ logbook, but no acccess to LDC or GDC directly
OCDB - Calibration parameters are stored in the Offline Calibration DB. The data used to calculate these parameters, the reference data, can also be optionally archived for later access from offline.
 
[1]
Yves Schutz:
128*32 = 512 B
[2]
Yves Schutz:
64*32 = 256 B