Cargando…

ATLAS Tile Calorimeter Conditions Database architecture and operations in Run 2

An overview of the Conditions Database (DB) structure for the hadronic Tile Calorimeter (TileCal), one of the ATLAS Detector sub-systems, is presented. ATLAS Conditions DB stores the data on the ORACLE backend, and the design and implementation has been developed using COOL (Conditions Objects for L...

Descripción completa

Detalles Bibliográficos
Autores principales: Smirnov, Iouri, Chakraborty, Dhiman, Solodkov, Alexander, Harkusha, Siarhei
Lenguaje:eng
Publicado: 2020
Materias:
Acceso en línea:https://dx.doi.org/10.1051/epjconf/202024502006
http://cds.cern.ch/record/2709282
Descripción
Sumario:An overview of the Conditions Database (DB) structure for the hadronic Tile Calorimeter (TileCal), one of the ATLAS Detector sub-systems, is presented. ATLAS Conditions DB stores the data on the ORACLE backend, and the design and implementation has been developed using COOL (Conditions Objects for LCG) software package as a common persistency solution for the storage and management of the conditions data. TileCal conditions and calibration data are stored in 4 separate Databases (DB) also known as schemas: TileCal Online and Offline DBs for data, DB for Monte Carlo simulation and Detector Control System DB. In order to support the smooth TileCal operations during the data taking period, experts perform the necessary calibrations, add the changes of detector status and other conditions data, prepare new conditions for data reprocessing and Monte Carlo production campaigns, and upload the new up-to-date information into DB using the custom-made software tools. The procedure of TileCal conditions’ preparation, validation and uploading to DBs is described, and some DB-related statistics collected in Run 2 is provided.