Transcript PPT file format 2.4M

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
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.
RDMS CMS 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
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)
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.
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)
Detector Subsystems Data
Equipment and construction
data
Oracle - WEB access &
management system
Calibration
Oracle - C API access
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 LIT JINR 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)
Databases & storage system structure
DB server:
Equipment DB
Calibration DB
API interface
Client
Files manipulating
Da
ta
&
fil
es
m
an
ip
ul
at
in
g
DB server
Mass storage
system
(CASTOR)
c
Ba
ku
p
W
EB
in
te
r fa
ce
WEB
Server
Client
es
Fil
s&
ad
o
l
Up
s
ad
nlo
w
Do
Data
Storage
This structure is to be realized
both at CERN and JINR
in the same way
ME Database Scheme
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.
ME1/1 Database
Web-interfaces:
 Equipment DB viewer - http://cms-equip.jinr.ru
 Equipment DB filling - http://calib.jinr.ru
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
HE Database scheme
“Source tubes lengths measurement on
HE”: Start page
Environment
“Source tubes lengths
measurement on HE”: Select
detector  Select zone
• At CERN:
Data is placed at CERN DEVDB Oracle server
Web part based on Oracle Application Server and written
on PL/SQL
• At JINR
“Source tubes lengths
measurement
on HE”: Select
Search results on
Linux
detector  Select zone 
selected criteria
Select port
Oracle
HTTP service
ROOT support
Tubes measurements URL: http://calib.jinr.ru/tubes/mainp.html
API access to ORACLE
Offline
calibration
software
Oracle_bridge.so
Oracle OCI
(module)
ORACLE Database
Server
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 module features
• Scalability
• Maximum operating speed
• Simple use
HF Data
 Wedge calibration
 Beam wedge calibration
 Channel calibration
Environment:
At CERN:
Database is placed at CERN DEVDB Oracle
server.
HF Database Scheme
Very first approach!
HF Database Scheme
Next stage!
Various stages of navigation on HF Data by Web
Various stages of navigation on HF Data by Web
Various stages of navigation on HF Data by Web
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
THANKS A LOT FOR YOUR ATTENTION!