The CMS event builder and storage system

G. Bauer; B. Beccati; U. Behrens; K. Biery; A. Brett; J. Branson; E. Cano; H. Cheung; M. Ciganek; S. Cittolin; A. Coarasa; C. Deldicque; E. Dusinberre; S. Erhan; F. F. Rodrigues; D. Gigi; F. Glege; R. Gomez-Reino; J. Gutleber; D. Hatton; M. Klute; J. F. Laurens; C. Loizides; J. A. Lopez Perez; F. Meijers; E. Meschi; A. Meyer; R. K. Mommsen; R. Moser; V. O'Dell; A. Oh; L. Orsini; V. Patras; C. Paus; A. Petrucci; M. Pieri; A. Racz; H. Sakulin; M. Sani; P. Schieferdecker; C. Schwick; J. F. Serrano Margaleff; D. Shpakov; S. Simon; K. Sumorok; M. Zanetti

doi:10.1088/1742-6596/219/2/022038

The CMS event builder and storage system

G. Bauer, B. Beccati, U. Behrens, K. Biery, A. Brett, J. Branson, E. Cano, H. Cheung, M. Ciganek, S. Cittolin, A. Coarasa, C. Deldicque, E. Dusinberre, S. Erhan, F. F. Rodrigues, D. Gigi, F. Glege, R. Gomez-Reino, J. Gutleber, D. HattonM. Klute, J. F. Laurens, C. Loizides, J. A. Lopez Perez, F. Meijers, E. Meschi, A. Meyer, R. K. Mommsen, R. Moser, V. O'Dell, A. Oh, L. Orsini, V. Patras, C. Paus, A. Petrucci, M. Pieri, A. Racz, H. Sakulin, M. Sani, P. Schieferdecker, C. Schwick, J. F. Serrano Margaleff, D. Shpakov, S. Simon, K. Sumorok, M. Zanetti

Research output: Contribution to journal › Article › peer-review

Abstract

The CMS event builder assembles events accepted by the first level trigger and makes them available to the high-level trigger. The event builder needs to handle a maximum input rate of 100 kHz and an aggregated throughput of 100 GB/s originating from approximately 500 sources. This paper presents the chosen hardware and software architecture. The system consists of 2 stages: an initial pre-assembly reducing the number of fragments by one order of magnitude and a final assembly by several independent readout builder (RU-builder) slices. The RU-builder is based on 3 separate services: the buffering of event fragments during the assembly, the event assembly, and the data flow manager. A further component is responsible for handling events accepted by the high-level trigger: the storage manager (SM) temporarily stores the events on disk at a peak rate of 2 GB/s until they are permanently archived offline. In addition, events and data-quality histograms are served by the SM to online monitoring clients. We discuss the operational experience from the first months of reading out cosmic ray data with the complete CMS detector. © 2010 IOP Publishing Ltd.

Original language	English
Article number	022038
Journal	Journal of Physics: Conference Series
Volume	219
Issue number	1
DOIs	https://doi.org/10.1088/1742-6596/219/2/022038
Publication status	Published - 2010

Access to Document

10.1088/1742-6596/219/2/022038

Cite this

Bauer, G., Beccati, B., Behrens, U., Biery, K., Brett, A., Branson, J., Cano, E., Cheung, H., Ciganek, M., Cittolin, S., Coarasa, A., Deldicque, C., Dusinberre, E., Erhan, S., Rodrigues, F. F., Gigi, D., Glege, F., Gomez-Reino, R., Gutleber, J., ... Zanetti, M. (2010). The CMS event builder and storage system. Journal of Physics: Conference Series, 219(1), Article 022038. https://doi.org/10.1088/1742-6596/219/2/022038

@article{c50554bd58e940ba86946abcb9caddcc,

title = "The CMS event builder and storage system",

abstract = "The CMS event builder assembles events accepted by the first level trigger and makes them available to the high-level trigger. The event builder needs to handle a maximum input rate of 100 kHz and an aggregated throughput of 100 GB/s originating from approximately 500 sources. This paper presents the chosen hardware and software architecture. The system consists of 2 stages: an initial pre-assembly reducing the number of fragments by one order of magnitude and a final assembly by several independent readout builder (RU-builder) slices. The RU-builder is based on 3 separate services: the buffering of event fragments during the assembly, the event assembly, and the data flow manager. A further component is responsible for handling events accepted by the high-level trigger: the storage manager (SM) temporarily stores the events on disk at a peak rate of 2 GB/s until they are permanently archived offline. In addition, events and data-quality histograms are served by the SM to online monitoring clients. We discuss the operational experience from the first months of reading out cosmic ray data with the complete CMS detector. {\textcopyright} 2010 IOP Publishing Ltd.",

author = "G. Bauer and B. Beccati and U. Behrens and K. Biery and A. Brett and J. Branson and E. Cano and H. Cheung and M. Ciganek and S. Cittolin and A. Coarasa and C. Deldicque and E. Dusinberre and S. Erhan and Rodrigues, {F. F.} and D. Gigi and F. Glege and R. Gomez-Reino and J. Gutleber and D. Hatton and M. Klute and Laurens, {J. F.} and C. Loizides and {Lopez Perez}, {J. A.} and F. Meijers and E. Meschi and A. Meyer and Mommsen, {R. K.} and R. Moser and V. O'Dell and A. Oh and L. Orsini and V. Patras and C. Paus and A. Petrucci and M. Pieri and A. Racz and H. Sakulin and M. Sani and P. Schieferdecker and C. Schwick and {Serrano Margaleff}, {J. F.} and D. Shpakov and S. Simon and K. Sumorok and M. Zanetti",

year = "2010",

doi = "10.1088/1742-6596/219/2/022038",

language = "English",

volume = "219",

journal = "Journal of Physics: Conference Series",

issn = "1742-6596",

publisher = "IOP Publishing Ltd",

number = "1",

}

Bauer, G, Beccati, B, Behrens, U, Biery, K, Brett, A, Branson, J, Cano, E, Cheung, H, Ciganek, M, Cittolin, S, Coarasa, A, Deldicque, C, Dusinberre, E, Erhan, S, Rodrigues, FF, Gigi, D, Glege, F, Gomez-Reino, R, Gutleber, J, Hatton, D, Klute, M, Laurens, JF, Loizides, C, Lopez Perez, JA, Meijers, F, Meschi, E, Meyer, A, Mommsen, RK, Moser, R, O'Dell, V, Oh, A, Orsini, L, Patras, V, Paus, C, Petrucci, A, Pieri, M, Racz, A, Sakulin, H, Sani, M, Schieferdecker, P, Schwick, C, Serrano Margaleff, JF, Shpakov, D, Simon, S, Sumorok, K & Zanetti, M 2010, 'The CMS event builder and storage system', Journal of Physics: Conference Series, vol. 219, no. 1, 022038. https://doi.org/10.1088/1742-6596/219/2/022038

TY - JOUR

T1 - The CMS event builder and storage system

AU - Bauer, G.

AU - Beccati, B.

AU - Behrens, U.

AU - Biery, K.

AU - Brett, A.

AU - Branson, J.

AU - Cano, E.

AU - Cheung, H.

AU - Ciganek, M.

AU - Cittolin, S.

AU - Coarasa, A.

AU - Deldicque, C.

AU - Dusinberre, E.

AU - Erhan, S.

AU - Rodrigues, F. F.

AU - Gigi, D.

AU - Glege, F.

AU - Gomez-Reino, R.

AU - Gutleber, J.

AU - Hatton, D.

AU - Klute, M.

AU - Laurens, J. F.

AU - Loizides, C.

AU - Lopez Perez, J. A.

AU - Meijers, F.

AU - Meschi, E.

AU - Meyer, A.

AU - Mommsen, R. K.

AU - Moser, R.

AU - O'Dell, V.

AU - Oh, A.

AU - Orsini, L.

AU - Patras, V.

AU - Paus, C.

AU - Petrucci, A.

AU - Pieri, M.

AU - Racz, A.

AU - Sakulin, H.

AU - Sani, M.

AU - Schieferdecker, P.

AU - Schwick, C.

AU - Serrano Margaleff, J. F.

AU - Shpakov, D.

AU - Simon, S.

AU - Sumorok, K.

AU - Zanetti, M.

PY - 2010

Y1 - 2010

N2 - The CMS event builder assembles events accepted by the first level trigger and makes them available to the high-level trigger. The event builder needs to handle a maximum input rate of 100 kHz and an aggregated throughput of 100 GB/s originating from approximately 500 sources. This paper presents the chosen hardware and software architecture. The system consists of 2 stages: an initial pre-assembly reducing the number of fragments by one order of magnitude and a final assembly by several independent readout builder (RU-builder) slices. The RU-builder is based on 3 separate services: the buffering of event fragments during the assembly, the event assembly, and the data flow manager. A further component is responsible for handling events accepted by the high-level trigger: the storage manager (SM) temporarily stores the events on disk at a peak rate of 2 GB/s until they are permanently archived offline. In addition, events and data-quality histograms are served by the SM to online monitoring clients. We discuss the operational experience from the first months of reading out cosmic ray data with the complete CMS detector. © 2010 IOP Publishing Ltd.

AB - The CMS event builder assembles events accepted by the first level trigger and makes them available to the high-level trigger. The event builder needs to handle a maximum input rate of 100 kHz and an aggregated throughput of 100 GB/s originating from approximately 500 sources. This paper presents the chosen hardware and software architecture. The system consists of 2 stages: an initial pre-assembly reducing the number of fragments by one order of magnitude and a final assembly by several independent readout builder (RU-builder) slices. The RU-builder is based on 3 separate services: the buffering of event fragments during the assembly, the event assembly, and the data flow manager. A further component is responsible for handling events accepted by the high-level trigger: the storage manager (SM) temporarily stores the events on disk at a peak rate of 2 GB/s until they are permanently archived offline. In addition, events and data-quality histograms are served by the SM to online monitoring clients. We discuss the operational experience from the first months of reading out cosmic ray data with the complete CMS detector. © 2010 IOP Publishing Ltd.

U2 - 10.1088/1742-6596/219/2/022038

DO - 10.1088/1742-6596/219/2/022038

M3 - Article

SN - 1742-6596

VL - 219

JO - Journal of Physics: Conference Series

JF - Journal of Physics: Conference Series

IS - 1

M1 - 022038

ER -

The CMS event builder and storage system

Abstract

Access to Document

Fingerprint

Cite this