RDMS CMS DataBases: Current Status, Development and Plans.

1. RDMS CMS DataBases: Current Status, Development and Plans. D.A Oleinik, A.Sh. Petrosyan, R.N.Semenov, I.A. Filozova V.V Korenkov, P.V. Moissenz, A. Vishnevskii, V. Karjavin Joint Institute for Nuclear Research, Dubna, Russia NEC’05

2. Russia and Dubna Member States(RDMS) • Russia and Dubna Member States(RDMS) - an organizational structure providing the necessary strength to take responsibility for the construction of detectors for CMS. • RDMSCMS concentrates the most of its efforts at design, building, commissioning and operation of substantial parts of the CMS detector in a number of areas and in particular, in: • Endcap Hadron Calorimeter • Forward muon station • Very Forward calorimeter

3. Databases RDMS CMS development and support. Opening remarks. • Within the frameworks of this activity works on the databases CMS development and support are carried out in JINR. • Some features of a solved problem: • Subject Domain is very extensive and complex • A large number of the participants of the works • Wide range of the information requirements of the future users • Requirements of all potential users should be satisfied • Necessity of the databases designing for essential and current problems (most often ways of the access to data  efficiency) • Providing the informational supporting of the subject domain as a whole( flexibility, adaptability)

4. Databases RDMS CMS development and support. Using approaches. Necessity to join such inconsistent requirements as flexibility and efficiency using both subject and applied approaches. Subject approach is used for the building of the basic informational structure, but applied approach — for the improvement to increment efficiency of the data processing and expansion of the functionality.

5. Databases structure and hierarchy. • Equipment management database • Holds structured data about all detectors parts as equipment elements • Construction databases • Holds all information about relations between different equipment elements • Configuration database • Holds all information required to bring the detector in any running mode • Conditions database • Holds all information about detector conditions (data on operating conditions)

6. Detector Subsystems Data • Equipment and construction data • Oracle - WEB access & management system • Calibration • Oracle - C API access

7. Equipment Database. • Equipment database is intended for storage of the information about equipment of various parts of the CMS detector. • ME1/1 Database: requirements • ME1/1 Database is a part of EndCap Database, which is designed by LITJINR database group. • Necessity of storing of large different types of data concerned with equipment such as specification information, results of tests and calibrations, traveler lists (equipment history) and so on. • Data can have different representations: files (test results, documentation), structured data (equipment specifications, relations between equipment), combined data (calibrations results)

8. Databases & storage system structure This structure is to be realized both at CERN and JINR in the same way

9. ME Database Scheme

10. ME1/1 ME1/1 Database: environment • Database server: Oracle (provided by CERN IT and JINR LIT) • WEB Server: Internet Information Server (Provided by CERN IT) ME1/1 Database: User Interfaces • Web interface – provides the initial filling of database, different access levels for users, information search on different criterions, adding and updating data.

11. ME1/1 Database Web-interfaces: • Equipment DB viewer - http://cms-equip.jinr.ru • Equipment DB filling - http://calib.jinr.ru

12. HE Data • Tubes lengths measurements The following types of data are stored for each tube: length of plastic tube, length of metal tube, estimated length of tube, measured length of tube, classification tags of "problem tubes" • Radioactive source calibration Measurement parameters

13. HE Database scheme

14. “Source tubes lengths measurement on HE”:Select detector  Select zone “Source tubes lengths measurement on HE”: Start page “Source tubes lengths measurement on HE”:Select detector  Select zone  Select port Search results on selected criteria Environment • At CERN: Data is placed at CERN DEVDB Oracle server Web part based on Oracle Application Server and written on PL/SQL • At JINR Linux Oracle HTTP service ROOT support Tubes measurements URL: http://calib.jinr.ru/tubes/mainp.html

15. API access to ORACLE Offline calibration software ORACLE Database Server Oracle_bridge.so (module) Oracle OCI handle = dlopen ("orca_oracle.so", RTLD_NOW); if (!handle) { fprintf (stderr, "%s\n", dlerror()); return 1; } c = (int (*)(double [64000])) dlsym(handle,"sqlloadmap"); } Oracle_bridge.so modulefeatures • Scalability • Maximum operating speed • Simple use

16. HF Data • Wedge calibration • Beam wedge calibration • Channel calibration Environment: At CERN: Database is placed at CERN DEVDB Oracle server.

17. HF Database Scheme Very first approach!

18. HF Database Scheme Next stage!

19. Various stages of navigation on HF Data by Web

20. Various stages of navigation on HF Data by Web

21. Various stages of navigation on HF Data by Web

22. SUMMARY Nearest plans – to continue the works on different subsystems databases development within frameworks RDMS CMS responsibility, in particular: • Construction Database improvement • To continue Calibration and Equipment Databases integration • User WEB-interfaces improvement • Uniform realization of storage system structure at CERN and JINR …

23. THANKS A LOT FOR YOUR ATTENTION!