| Authors |
Amoiridis, Vassileios ; Behrens, Ulf ; Bocci, Andrea ; Branson, James ; Brummer, Philipp ; Cano, Eric ; Cittolin, Sergio ; Da Quintanilha, Joao Da Silva Almeida ; Darlea, Georgiana-Lavinia ; Deldicque, Christian ; Dobson, Marc ; Dvorak, Antonin ; Gigi, Dominique ; Glege, Frank ; Gomez-Ceballos, Guillelmo ; Gorniak, Patrycja ; Gutic, Neven ; Hegeman, Jeroen ; Moreno, Guillermo Izquierdo ; James, Thomas Owen ; Karimeh, Wassef ; Kartalas, Miltiadis ; Krawczyk, Rafal Dominik ; Li, Wei ; Long, Kenneth ; Meijers, Frans ; Meschi, Emilio ; Morovic, Srecko ; Orsini, Luciano ; Paus, Christoph ; Petrucci, Andrea ; Pieri, Marco ; Rabady, Din-yar Sebastian ; Racz, Attila ; Rizopoulos, Theodoros ; Sakulin, Hannes ; Schwick, Christoph ; Šimelevičius, Dainius ; Tzanis, Polyneikis ; Velez, Cristina Vazquez ; Zejdl, Petr ; Zhang, Yousen ; Zogatova, Dominika |
| Abstract [eng] |
The data acquisition (DAQ) of the Compact Muon Solenoid (CMS) experiment at CERN, collects data for events accepted by the Level-1 Trigger from the different detector systems and assembles them in an event builder prior to making them available for further selection in the High Level Trigger, and finally storing the selected events for offline analysis. In addition to the central DAQ providing global acquisition functionality, several separate, so-called “MiniDAQ” setups allow operating independent data acquisition runs using an arbitrary subset of the CMS subdetectors. During Run 2 of the LHC, MiniDAQ setups were running their event builder and High Level Trigger applications on dedicated resources, separate from those used for the central DAQ. This cleanly separated MiniDAQ setups from the central DAQ system, but also meant limited throughput and a fixed number of possible MiniDAQ setups. In Run 3, MiniDAQ-3 setups share production resources with the new central DAQ system, allowing each setup to operate at the maximum Level-1 rate thanks to the reuse of the resources and network bandwidth. Configuration management tools had to be significantly extended to support the synchronization of the DAQ configurations needed for the various setups. We report on the new configuration management features and on the first year of operational experience with the new MiniDAQ-3 system. |
