1 / 16

Condition Database

Condition Database. F. Cavallari (INFN Roma) with input from: R. Egeland, R. Alemany, G. Organtini, G. Dissertori, F. Glege, S. Rahatlou, A. Branson, N. Toth. CONSTRUCTION DB. EMDB/DDD (cables Channels Connections Boards Crates History). A.B. and N.T. R.E. and G.O.

zachery-shepherd
Download Presentation

Condition Database

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Condition Database F. Cavallari (INFN Roma) with input from: R. Egeland, R. Alemany, G. Organtini, G. Dissertori, F. Glege, S. Rahatlou, A. Branson, N. Toth

  2. CONSTRUCTION DB EMDB/DDD (cables Channels Connections Boards Crates History) A.B. and N.T. R.E. and G.O. CONFIGURATION DB (Channel settings) CONDITIONS DB (DCS Conditions DAQ/TRIG Conditions Monitoring info calibrations) R.A. DAQ data DCS data R.A. ?? R.A. DAQ TRIG TOKR DCS-PVSS Laser Monitoring Farm Physics Analysis ORCA HLT farm G.D. R.A. P. B. E. V. P.V. A.H. R.B. S.R.

  3. Data flow Online Master Data Storage Offline Reconstruction Conditions DB ONline subset Equipment Configuration Conditions Create rec conDB data set Calibration Conditions Conditions Configuration Master copy Offline Reconstruction Conditions DB OFfline subset Bat 513 From Frank Glege

  4. Data flow 1 account at the IT ORACLE server for off-line database Online Master Data Storage Offline Reconstruction Conditions DB ONline subset 1 PC at the test-beam with ORACLE (data from DCS, monitoring, Token Ring, …) Equipment Configuration Conditions Create rec conDB data set Calibration Conditions Conditions Configuration Master copy Offline Reconstruction Conditions DB OFfline subset Bat 513 H4 (cosmics and test-beam) From Frank Glege

  5. DATA from the Construction DB

  6. DATA FROM DCS-PVSS

  7. DATA FROM TOKEN RING

  8. DATA from off-detector electronics monitoring • The local Data Acquisition System would like to store in the conditions database some data useful for plotting histograms online and for identifying problems. Here is a list of some ideas about what could be stored: • Status of electronic boards (status registers, monitoring counters, error counters) • Verification of TTS status (Ready, Busy, Overflow, OutofSync) • Verification of data integrity using spy events • Check clock phase stability using spy events • Check trigger primitives computation using spy events • Check zero suppression and selective readout algorithms with spy/unbiased events • Check synchronization of trigger data analyzing SLB histograms • Build histograms of bunch occupancy with spy events (check synchronization of DAQ data) • Build histograms of pulse height of detector and trigger channels • Build other physics monitoring items (e.g. occupancy histograms, E.M. cluster histograms, etc.) From J. V. talk June 2004

  9. DATA FROM THE MONITORING

  10. DATA from the offline analysis

  11. Schema of the online cond DB channelView Lists all channels and mappings from one kind of channel to another. viewDescription Metadata for each channelView. COND_<type> One data table for each type of condition. Data is identified by its logic_idand IoV (since, till). Data is usually a single value, but can also be a value with an error measurement or an array of values, value-error pairs. conditionDescription Metadata for each <type> of condition. Includes description, units, and information for applications to determine what the type and size of array is. By Rick Egeland and G. Organtini

  12. How to use the channelView Table

  13. Schema of the off-line cond db • Substantially the same as for the online but the data are regrouped in 1 row per condition for the whole calorimeter barrel. • Some parameter smoothing, removal of bad readings, is foreseen in moving from the online to offline DB. Experts of each sub-system will do/decide how to do this transfer.

  14. How to write to the Cond DB • From PVSS: use archiving method of PVSS and F.G. receipe to trigger writing in cond DB (to be tested ?) • From CCS Supervisor use OCCI with simple SQL statements (to be tested) • From Monitoring farm (c++ software?) use OCCI For OCCI reference: http://www.stanford.edu/dept/itss/docs/oracle/9i/appdev.920/a96583/cci01int.htm or http://oradoc.cern.ch

  15. How to read the Cond DB From ORCA we will access the off-line cond db. S. Rahatlou is now implementing the changes in the ORCA classes to use the database. R. Egeland will develop an interface to the online DB to query the data

  16. Conclusions • The plan for the Condition DB is more or less clear • But there is a lot of work to be done • Soon we need effort from the developers of the various applications to write in the database • Thanks to all people in the DDH Group!

More Related