Development of the CMS Databases and Interfaces for CMS Experiment: Current Status and Future Plans D.A Oleinik, A.Sh. Petrosyan, R.N.Semenov, I.A. Filozova, V.V. Korenkov, E.G. Nikonov, E.A. Tikhonenko Joint Institute for Nuclear Research, Dubna, Russia NEC’07

Works started in May 2004 First stage — collecting of the information about detector and data relations Findings: not practical to create a static relational model for all detector parts with all necessary relations between parts and the information collected, need the infrastructure to support evolving self-described database identified Second stage – spring New extensible database structure. First realization for CMS ME1/1 System DB, initial filling of Endcap Hadronic Calorimeter DB. Introduction

Database Structure Data on the equipment units have been collected Possibility to build the unique data structure for each equipment group Extensible DB structure provides possibility to describe equipment independently of the equipment unit physical model (Abstract equipment definition structure). DB structure supports ‘blocks’ of storage: – links to unstructured information (files) – relations with tests results (calibrations and other information committed with conditions)

Hierarchy Levels I Level — Subsystem definition II Level — Equipment group definition in the subsystem frameworks III Level — Equipment subgroup definition in the group frameworks IV Level — Equipment unit description.

DB Logical Model

System Overview User is able to define a hierarchy, a full data set and additional unstructured files for every equipment element Group parameters and values definition Equipment unit properties definition Ability to load files linked to entity Equipment logs (equipment traveler list) Tests results

DB Structure

Equipment log provides possibility of event registration like installation, maintenance, etc. List of events defined for each group of equipment Equipment Log

A lot of information is provided in an unstructured form: –Special raw data –Images –Files To manipulate this kind of data, a special subsystem connected with mass storage system was developed Unstructured Information

Interfaces Interfaces to DB –WEB interface –API interface to conditions data –O2O interface

API Interfaces Due to a specificity of the DB schema, API interfaces have been organized differently for different subdetectors. Now the API to HE calibration data is fully realized. HE calibration API: C++ to Oracle API based on OCCI API can add, update, delete and select information Selection can be done by different parameters: Tile code Date Date interval Data processing operator name

WEB Interface

O2O Interface O2O (online to offline) – procedure of the data transmission from online (relational) DB to offline (POOL) database. Current realization of O2O code works in CMSSW framework. OCCI interface is used for accessing to OnlineDB (Oracle) and access to OfflineDB is provided by PoolDBOutputService

Information System Schema

Some Statistics Database Current capacity: 1.2 GB Disk storage Capacity: 42 TB disk massive at JINR (dCache) 0.4 TB buffer storage at CERN + CASTOR resources Data volumes Database: 30,000 records (~ 500 MB) Raw files: 600 GB

Summary  Subject domain and informational requirements analysis was carried out.  It gave possibility to define the basic entities set and the relations between them.  Database logical&physical model was developed  Database has been filled and is in practical use.  Different interface types to DB were realized.  Current work: unification of the equipment and construction DB for Muon CSC Database will content: all information about chambers, electronics, cables and other parts including equipment tracking and results of tests

Future Plans Positive feedback in pre-production operations prepared database for deployment in production Software development for the updating chambers test results from files Structure creation for the additional electronics information storing API development for the access to the initial electronics calibration constants Further DB filling User interfaces improvement Expected growth of data volumes: up to half million of the records (5 GB) in DB up to 6 TB in raw files

THANKS A LOT FOR YOUR ATTENTION!