Rdms cms databases current status development and plans
This presentation is the property of its rightful owner.
Sponsored Links
1 / 23

RDMS CMS DataBases: Current Status, Development and Plans. PowerPoint PPT Presentation


  • 85 Views
  • Uploaded on
  • Presentation posted in: General

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).

Download Presentation

RDMS CMS DataBases: Current Status, Development and Plans.

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Rdms cms databases current status development and plans

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)

  • 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


Databases rdms cms development and support opening remarks

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

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

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

Detector Subsystems Data

  • Equipment and construction data

  • Oracle - WEB access & management system

  • Calibration

  • Oracle - C API access


Equipment database

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)


  • Databases storage system structure

    Databases & storage system structure

    This structure is to be realized

    both at CERN and JINR

    in the same way


    Me database scheme

    ME Database Scheme


    Me1 1

    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

    ME1/1 Database

    Web-interfaces:

    • Equipment DB viewer - http://cms-equip.jinr.ru

    • Equipment DB filling - http://calib.jinr.ru


    He data

    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

    HE Database scheme


    Environment

    “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


    Api access to oracle

    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


    Hf data

    HF Data

    • Wedge calibration

    • Beam wedge calibration

    • Channel calibration

      Environment:

      At CERN:

      Database is placed at CERN DEVDB Oracle server.


    Hf database scheme

    HF Database Scheme

    Very first approach!


    Hf database scheme1

    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 web1

    Various stages of navigation on HF Data by Web


    Various stages of navigation on hf data by web2

    Various stages of navigation on HF Data by Web


    Summary

    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


    Rdms cms databases current status development and plans

    THANKS A LOT FOR YOUR ATTENTION!


  • Login