Persistent storage of non-event data in the CMS databases
M. De Gruttola, S. Di Guida, D. Futyan, F. Glege, G. Govi, V., Innocente, P. Paolucci, P. Picca, A. Pierro, D. Schlatter, Z. Xie
TL;DR
This paper discusses the architecture and implementation of persistent storage solutions for non-event data in the CMS experiment's databases, highlighting data management and system performance during cosmic data collection.
Contribution
It introduces the CMS condition database architecture, data-flow, and the PopCon tool for populating offline databases, with practical insights from 2008-2009 cosmic data runs.
Findings
Successful deployment of the database system during cosmic data taking
Effective data management with PopCon tool
Performance meets experiment requirements
Abstract
In the CMS experiment, the non event data needed to set up the detector, or being produced by it, and needed to calibrate the physical responses of the detector itself are stored in ORACLE databases. The large amount of data to be stored, the number of clients involved and the performance requirements make the database system an essential service for the experiment to run. This note describes the CMS condition database architecture, the data-flow and PopCon, the tool built in order to populate the offline databases. Finally, the first experience obtained during the 2008 and 2009 cosmic data taking are presented.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.