1 / 9

Collision data workflow

Michele de Gruttola 2008 Report: Online to Offline tool for non event data data transferring using database. Collision data workflow. Raw data (Event data) . CMSSW. Condition data (Non event data).

willa
Télécharger la présentation

Collision data workflow

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. Michele de Gruttola 2008 Report:Online to Offline tool for non event data data transferring using database

  2. Collision data workflow Raw data (Event data) CMSSW Condition data (Non event data) Data taken from the detectors can be divided in event data (RAW data) collecting the physical responses of the detector devices to collisions, and non event data, such as the conditions of the detector (magnetic field value, status of the electronic devices, currents….) and calibration of the various subdetector components (alignment, drift time values of the drift tube, pedestals mean and error, noise, Lorentz angle of the strip). Both event data and non event data are needed to properly reconstruct all physical quantities

  3. Conditions/calibrations workflow Conditions data are saved in Oracle database and transferred from online network (physically at CERN P5) to offline network (CERN network and so to the all communities and institutes) Relational Databases (OMDS, Online Master Data Storage) Pool-ORA db (ORCOFF, Offline Reconstraction Condition DB OFFline Set Pool-ORA db (ORCON, Offline Reconstraction Condition DB ONline Set POPCON Automatic streaming POPCON ONLINE OFFLINE

  4. Why databases for conditions? • Condition/calibration data are very important to validate and correctly analyze collision data, and a correct understating of condition quantities, and the possibility to update, recalculate and retrieve them is very critical during the overall life and activity of the experiment. • Condition/Calibration data event are almost .5 TB per year • Many efforts has been devoted to develop and testing a robust storing/transferring/retrieving system using Oracle-Database and Pool-Ora technology. Calibration/Condition data coming form online network (i.e. in the detector computers and devices’ network), from different sources (databases, txt files, root file, etc.) are packed as C++ object and moved in the Online condition database (ORCON) via a dedicated package called PopCon (Populator of Condition Objects) fully integrated in the overall CMSSW. The data are then automatically streamed to the offline database (ORCOFF) and so accessible in the offline network as C++ object. This mechanism has been intensively and succesfully used during 2008 tests with cosmic rays.

  5. PopCon feautures (1) • PopCon (Populator of Condition) has been ideated by V. Innocente…… The application is currently under mine responsibility and has been improved this year, deployed and applied to all subsystems • PopCon encapsulate data coming from different sources (txt, xml file as typical from calibration output of offline C++/CMSSW jobs, and relational table in OMDS, as typical for condition data) in Pool-ORA object, i.e. in C++ classes in a proper format to be stored in Oracle database, and retrievable as pool-object (i.e. compatible with ROOT framework, as the Event data themselves). • PopCon assign to every condition/calibration object an IOV (Interval of validity) as run number or timestamp (microseconds from 1/1/1970 in UTC) • PopCon assign a tag to the data. A new tag correspond to a new recalculated calibrations • All coherent tags are grouped in a global tag, and retrieved OFFLINE with Frontier technology • PopCon provide also a log every transaction. Thanks to that a complete transaction history monitor has been be set up.

  6. calibrations 56000 55000 IOV • Ecal Pedestals • # mean rms • ……………….......... • ……………………... • 13 2 • 246 9 3 • ……………………... • …………………...... • Ecal Pedestals • # mean rms • ……………….......... • ……………………... • 10 1 • 246 11 2 • ……………………... • …………………...... CRAFT_EcalPed TAG

  7. conditions 121134567890 123456543890 IOV • RPC roll currents • # value • …………………….. • ……………………... • 23 11 • 24 13 • ……………………... • …………………...... • RPC roll currents • # value • …………………….. • ……………………... • 23 10 • 24 15 • ……………………... • …………………...... CRAFT_RPCHV TAG

  8. DB activity monitoting • PopCon provide also logging information for any transaction. Thanks to that a monitor tool has been set up POPCON daily applications run during CRAFT (13/10 14/11)

  9. Conclusions • Work done for detector condition/calibration data validation. • PopCon deployed successfully during data taking with cosmics data the tool has been applied to all subdetectors during CRAFT • I’m now the official translator between Vincenzo and the CMS community ;-)

More Related