ALICE Calibration Requirements  
 
 
TRD OK March 07
Par # Parameter Data format/size per channel Data size (Total) 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 implemented in[1] use case #
      on FES in OCDB (bytes) reference (bytes)                                                                          
1 position of supermodule (cm,deg) 18x6 float   400 0 year survey yes - - - DCDB yes sim and rec -
2 position of chamber (cm,deg) 540x6 float   1.20E+04 1.00E+08 hour HLT yes physics run 1e5 pp events - HLT FES/OCDB yes sim and rec 2
3 pad drift velocity factor 1.2e6 ushort   2.30E+06 8.00E+07 year HLT yes physics run 1e8 pp events - HLT FES/OCDB yes sim and rec 2
4 pad T0 (timebin) 1.2e6 ushort   2.30E+06 8.00E+07 year HLT yes physics run 1e8 pp events - HLT FES/OCDB yes sim and rec 2
5 pad gain factor 1.2e6 ushort   2.30E+06 1.50E+09 year HLT yes physics run 1e8 pp events - HLT FES/OCDB yes sim and rec 2
6 pad resp. func. Width (pad) 1.2e6 ushort   2.30E+06 5.00E+08 year HLT yes physics run 1e8 pp events - HLT FES/OCDB yes sim    2
7 chamber drift velocity (cm/timebin) 540 float   2.10E+03 4.00E+04 hour HLT yes physics run 1e5 pp events - HLT FES/OCDB yes sim and rec 2
8 chamber drift T0 (timebin) 540 float   2.10E+03 4.00E+04 hour HLT yes physics run 1e5 pp events - HLT FES/OCDB yes sim and rec 2
9 chamber gain 540 float   2.10E+03 7.00E+05 hour HLT yes physics run 1e5 pp events - HLT FES/OCDB yes sim and rec 2
10 dedx histogram2 55 hist   5.20E+04 0 year Offline  yes physics run or simulation - - OCDB yes rec -
11 max timebin histograms 55 hist   5.20E+04 0 year Offline  yes physics run or simulation - - OCDB yes rec -
12 clock frequency (MHz) 1 float   0 0 run Whatever (see note1)  yes - - - DCS FES/OCDB yes rec 5
13 number of timebins 1 int   1 0 run Config summary file  yes - - - DCS FES/OCDB yes sim and rec 5
14 tail cancellation tau1 1 int   0 0 run Config summary file  yes - - - DCS FES/OCDB yes ?  
15 tail cancellation tau2 1 int   0 0 run Config summary file  yes - - - DCS FES/OCDB yes ?  
16 tail cancellation amplitude 1 int   0 0 run Config summary file  yes - - - DCS FES/OCDB yes ?  
17 pedestal 1 int   0 0 run Config summary file  yes - - - DCS FES/OCDB yes ?  
18 configuration id 1024 char   1000 0 run Config summary file  yes - - - DCS FES/OCDB yes ?  
19 gain table id 1024 char   1000 0 year Config summary file  yes - - - DCS FES/OCDB yes ?  
20 status byte of superm 18 char   0 0 run Whatever (see note1)  yes - - - DCS FES/OCDB yes sim via config 5
21 status  byte of chamber 540 char   510 0 minute DCS Archive DB yes - - - DCS FES/OCDB yes sim 5
22 status  byte of MCM 6.7e4 char   510 0 run Whatever (see note1)  yes - - - DCS FES/OCDB yes sim 5
23 status  byte of pad 1.2e6 char   1.10E+06 0 run Config summary file  yes - - - DCS FES/OCDB yes sim 5
24 FEE gain correction 1.2e6 ushort   2.30E+06 0 run Whatever (see note1)  yes - - - DCS FES/OCDB yes - 5
25 ADC thresholds 1.2e6 char   6.40E+05 0 run Whatever (see note1)  yes - - - DCS FES/OCDB   - 5
26 pretrigger information 1024 char   1.00E+03 0 run DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
27 drift velocity monitor HV 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
28 drift velocity monitor peak1 pos 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
29 drift velocity monitor peak2 pos 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
30 drift velocity monitor peak1 area 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
31 drift velocity monitor peak2 area 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
32 drift velocity monitor temp1 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
33 drift velocity monitor temp2 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
34 drift velocity monitor pressure 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
35 drift velocity monitor velocity 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   ? 4
36 drift velocity monitor gain1 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
37 drift velocity monitor gain2 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
38 drift velocity monitor CO2 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
39 drift velocity monitor N2 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
40 environment temperature 540 float   210 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
41 chamber anode currents 540 float   210 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
42 chamber drift currents 540 float   210 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
43 chamber anode voltages 540 float   410 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
44 chamber drift volatges 540 float   410 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
45 low voltage voltage 1080 float   410 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
46 low voltage current 1080 float   410 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
47 atmospheric pressure 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
48 luminosity 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
49 magnetic field 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   sim/rec via config 4
50 O2 content in gas 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
51 chamber gas overpressure 1 float   0 0 minute DCS Archive DB yes - - - DCS ArchiveDB/OCDB   - 4
1.34E+07 2.26E+09
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.
Please note that the meaning of the last column is whether or not the variable is actually supposed to be used in the simulation and reconstruction software, and if yes, whether it has been implemented yet. (I changed its name ) The pink fields mean it is not quite sure yet that it is needed, red means it has to be implemented.
Note 1 solution 1:  whenever a configuration is loaded, the version number will be recorded in the PVSS archive. This version number can be accessed by the shutle. The full configuration record can be stored in the OCDB and the configuration version will be a pointer to this data. Drawback - all configuration data must be available on DCDB before its first use

Solution 2: the configuration parameters required by offline will always archived. Drawback: our archive will unecessary grow. As the stored information is not needed for DCS operation, I do not like this approach

Solution 3: the configuration parameters will be stored as files on the file exchange server and will be picked-up by shuttle. Now, the duplication of information will be on the OCDB side. 
[1]
Yves Schutz:
Implemented and tested end of september