Cargando…

The Data Quality Monitoring software for the CMS experiment at the LHC: past, present and future

The Data Quality Monitoring software is a central tool in the CMS experiment. It is used in the following key environments: (i) Online, for real-time detector monitoring; (ii) Offline, for the prompt-offline-feedback and final fine-grained data quality analysis and certification; (iii) Validation of...

Descripción completa

Detalles Bibliográficos
Autores principales: Azzolini, Virginia, van Besien, Broen, Bugelskis, Dmitrijus, Hreus, Tomas, Maeshima, Kaori, Fernandez Menendez, Javier, Norkus, Antanas, Patrick, James Fraser, Rovere, Marco, Schneider, Marcel Andre
Lenguaje:eng
Publicado: 2019
Materias:
Acceso en línea:https://dx.doi.org/10.1051/epjconf/201921402003
http://cds.cern.ch/record/2701776
_version_ 1780964594520424448
author Azzolini, Virginia
van Besien, Broen
Bugelskis, Dmitrijus
Hreus, Tomas
Maeshima, Kaori
Fernandez Menendez, Javier
Norkus, Antanas
Patrick, James Fraser
Rovere, Marco
Schneider, Marcel Andre
author_facet Azzolini, Virginia
van Besien, Broen
Bugelskis, Dmitrijus
Hreus, Tomas
Maeshima, Kaori
Fernandez Menendez, Javier
Norkus, Antanas
Patrick, James Fraser
Rovere, Marco
Schneider, Marcel Andre
author_sort Azzolini, Virginia
collection CERN
description The Data Quality Monitoring software is a central tool in the CMS experiment. It is used in the following key environments: (i) Online, for real-time detector monitoring; (ii) Offline, for the prompt-offline-feedback and final fine-grained data quality analysis and certification; (iii) Validation of all the reconstruction software production releases; (iv) Validation in Monte Carlo productions. Though the basic structure of the Run1 DQM system remains the same for Run2, between the Run1 and Run2 periods, the DQM system underwent substantial upgrades in many areas, not only to adapt to the surrounding infrastructure changes, but also to provide improvements to meet the growing needs of the collaboration with an emphasis on more sophisticated methods for evaluating data quality. We need to cope with the higher-energy and -luminosity proton-proton collision data, as well as the data from various special runs, such as Heavy Ion runs. In this contribution, we will describe the current DQM software, structure and workflow in the different environments. We then discuss the performance and our experiences with the DQM system in Run2. The main technical challenges which we have encountered and the solutions adopted during Run2 will also be discussed, including efficient use of memory in multithreading environments. Finally, we present the prospect of a future DQM upgrade with emphasis on functionality and long-term robustness for LHC Run3.
id oai-inspirehep.net-1760546
institution Organización Europea para la Investigación Nuclear
language eng
publishDate 2019
record_format invenio
spelling oai-inspirehep.net-17605462022-08-10T12:21:55Zdoi:10.1051/epjconf/201921402003http://cds.cern.ch/record/2701776engAzzolini, Virginiavan Besien, BroenBugelskis, DmitrijusHreus, TomasMaeshima, KaoriFernandez Menendez, JavierNorkus, AntanasPatrick, James FraserRovere, MarcoSchneider, Marcel AndreThe Data Quality Monitoring software for the CMS experiment at the LHC: past, present and futureDetectors and Experimental TechniquesComputing and ComputersThe Data Quality Monitoring software is a central tool in the CMS experiment. It is used in the following key environments: (i) Online, for real-time detector monitoring; (ii) Offline, for the prompt-offline-feedback and final fine-grained data quality analysis and certification; (iii) Validation of all the reconstruction software production releases; (iv) Validation in Monte Carlo productions. Though the basic structure of the Run1 DQM system remains the same for Run2, between the Run1 and Run2 periods, the DQM system underwent substantial upgrades in many areas, not only to adapt to the surrounding infrastructure changes, but also to provide improvements to meet the growing needs of the collaboration with an emphasis on more sophisticated methods for evaluating data quality. We need to cope with the higher-energy and -luminosity proton-proton collision data, as well as the data from various special runs, such as Heavy Ion runs. In this contribution, we will describe the current DQM software, structure and workflow in the different environments. We then discuss the performance and our experiences with the DQM system in Run2. The main technical challenges which we have encountered and the solutions adopted during Run2 will also be discussed, including efficient use of memory in multithreading environments. Finally, we present the prospect of a future DQM upgrade with emphasis on functionality and long-term robustness for LHC Run3.oai:inspirehep.net:17605462019
spellingShingle Detectors and Experimental Techniques
Computing and Computers
Azzolini, Virginia
van Besien, Broen
Bugelskis, Dmitrijus
Hreus, Tomas
Maeshima, Kaori
Fernandez Menendez, Javier
Norkus, Antanas
Patrick, James Fraser
Rovere, Marco
Schneider, Marcel Andre
The Data Quality Monitoring software for the CMS experiment at the LHC: past, present and future
title The Data Quality Monitoring software for the CMS experiment at the LHC: past, present and future
title_full The Data Quality Monitoring software for the CMS experiment at the LHC: past, present and future
title_fullStr The Data Quality Monitoring software for the CMS experiment at the LHC: past, present and future
title_full_unstemmed The Data Quality Monitoring software for the CMS experiment at the LHC: past, present and future
title_short The Data Quality Monitoring software for the CMS experiment at the LHC: past, present and future
title_sort data quality monitoring software for the cms experiment at the lhc: past, present and future
topic Detectors and Experimental Techniques
Computing and Computers
url https://dx.doi.org/10.1051/epjconf/201921402003
http://cds.cern.ch/record/2701776
work_keys_str_mv AT azzolinivirginia thedataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT vanbesienbroen thedataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT bugelskisdmitrijus thedataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT hreustomas thedataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT maeshimakaori thedataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT fernandezmenendezjavier thedataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT norkusantanas thedataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT patrickjamesfraser thedataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT roveremarco thedataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT schneidermarcelandre thedataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT azzolinivirginia dataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT vanbesienbroen dataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT bugelskisdmitrijus dataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT hreustomas dataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT maeshimakaori dataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT fernandezmenendezjavier dataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT norkusantanas dataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT patrickjamesfraser dataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT roveremarco dataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture
AT schneidermarcelandre dataqualitymonitoringsoftwareforthecmsexperimentatthelhcpastpresentandfuture