1. Introduction CMS database workshop 23 rd to 25 th of February 2004 Frank Glege

2. 24.02.2004Frank Glege2 Database types We will have 4 kinds of databases in CMS: –Construction databases Holds all information about the sub detector construction up to the start of integration –Equipment management database Holds all information to physically set up the detector and is used for asset tracking –Configuration database Holds all information required to bring the detector in any running mode –Conditions database Holds all information about detector conditions

3. 24.02.2004Frank Glege3 Construction DBs Sub detector specific Sub detector responsibility Already existing for most sub detectors. Have to be available for the lifetime of CMS Data: construction info, initial calibration data, work flow info, etc. Data will partially be copied into the 3 other DBs.

4. 24.02.2004Frank Glege4 Equipment management DB Common for all CMS Set up by CMS integration, data entered and maintained by sub detectors Partially existing Data: detector and electronics parts, cables, racks, crates, location history of all items, etc… User interface existing (rack wizard) to enter required information. Needs time stamping. Few 100MB of live data

5. 24.02.2004Frank Glege5 Configuration DB Sub detector specific parts on front end electronics configuration, combined DAQ, Trigger and DCS info. Set up by corresponding groups Very few parts existing Data: see above Interface to online software framework XDAQ existing First prototype of interface to DCS existing Needs time stamping, versioning and tagging

6. 24.02.2004Frank Glege6 Conditions DB First interface definition by Pere Mato Implementations of this interface for Objectivity, mySQL and ORACLE existing Tools provided by LCG? Data: all parameters describing the run conditions and logging. Will be used for error tracking in the online system

7. 24.02.2004Frank Glege7 Conditions DB is an o?line DB Conditions DB Conditions DB Online data Offline data

8. 24.02.2004Frank Glege8 Constraints on physical implementation DB buffer IT DB buffer to ensure running in case of network loss Self contained persistent storage region

9. 24.02.2004Frank Glege9 The conditions DB data… Most of the conditions data is not used for offline reconstruction Most of the conditions data stays at the experiment Conditions data is the logging of the online system Conditions data will be used for error tracking in the online system Conditions data will be related to –Other conditions data –Event quality monitoring –Configuration data –…–…

10. 24.02.2004Frank Glege10 Condigurogging Configuration Conditions Logging Configuration Conditions Logging IT Conditions Calibration

11. 24.02.2004Frank Glege11 Logistics Architecture for writing conditions data –Simple api –Writer proxy –Direct access Utility for data transport IP5->IT –Configurable subset of data to be transferred –Data reduction? –Smoothing? –Generic – detector specific? Utility for data transport IT->IP5 –Configurable subset of data to be transferred Interface conditions data to reconstruction software?

12. 24.02.2004Frank Glege12 Data handling Initial population of database Data maintenance –Generic tool (hierarchical browsing sufficient)? –Specific graphical representation? Monitoring –Should be the same tool as for event monitoring –Must receive data from filter farm, front end electronics PCs, database, …