Online interactions with Databases

The following is known or assumed:

1. The online will access the online hardware DB, run configuration DB, calibration DB, Trigger Table DB, Run Conditions DB and CDF Conditions DB.
2. The online will write to the calibration DB (via a calibration consumer process) during a calibration run, and to the run conditions DB for all runs.
3. The Monitoring and Control System will write to the CDF conditions DB via an undecided mechanism. Note that it is currently planned that the CDF conditions DB will not be available to the CDF offline, so all information necessary offline needs to be written to the run conditions DB.
4. For the online hardware, there will be a calibration validation process that runs following a calibration run, and declares valid individual calibrations and produces the "Valid_Set" of calibrations spanning all of CDF. Run_Control promotes a "Valid_Set" to a "Used_Set" for that run if and when it actually uses the calibrations. This "Used_Set" will need to be accessed by the consumers and Stage0.

Documents

• Run Control: What Run Control is assuming about the databases is documented on page 20 and 21 of this draft document by the Run Control group.
• Monitoring Control System : Online monitoring of HV/LV/temp etc. They estimate they will access the online database once every 10 to 30 minutes and write 3 GByte per year.
• Requirements and Tests : Draft Document from Umesh Joshi on requirements for an Online Database and performance tests that he has done.
• Tests : Talk by Umesh Joshi on May 18, 1999, on tests for an Online Database.