Szczegóły publikacji
Opis bibliograficzny
Operation of the ATLAS trigger system in Run 2 / G. Aad, [et al.], L. ADAMCZYK, [et al.], T. BOŁD, [et al.], W. DĄBROWSKI, [et al.], I. GRABOWSKA-BOŁD, [et al.], K. W. JANAS, [et al.], P. A. JANUS, [et al.], S. KOPERNY, [et al.], I. K. ŁAKOMIEC, [et al.], K. MAJ, [et al.], B. MINDUR, [et al.], A. OGRODNIK, [et al.], P. PALNI, [et al.], M. PRZYBYCIEŃ, [et al.] // Journal of Instrumentation [Dokument elektroniczny]. — Czasopismo elektroniczne ; ISSN 1748-0221. — 2020 — vol. 15 iss. 10 art. no. P10004, s. [2], 1–57. — Wymagania systemowe: Adobe Reader. — Bibliogr. s. 37–41, Abstr. — Publikacja dostępna online od: 2020-10-02
Autorzy (2959)
Słowa kluczowe
Dane bibliometryczne
| ID BaDAP | 130844 |
|---|---|
| Data dodania do BaDAP | 2020-11-06 |
| Tekst źródłowy | URL |
| DOI | 10.1088/1748-0221/15/10/P10004 |
| Rok publikacji | 2020 |
| Typ publikacji | artykuł w czasopiśmie |
| Otwarty dostęp |  |
| Creative Commons | |
| Czasopismo/seria | Journal of Instrumentation |
Abstract
The ATLAS experiment at the Large Hadron Collider employs a two-level trigger system to record data at an average rate of 1 kHz from physics collisions, starting from an initial bunch crossing rate of 40 MHz. During the LHC Run 2 (2015-2018), the ATLAS trigger system operated successfully with excellent performance and flexibility by adapting to the various run conditions encountered and has been vital for the ATLAS Run-2 physics programme For proton-proton running, approximately 1500 individual event selections were included in a trigger menu which specified the physics signatures and selection algorithms used for the data-taking, and the allocated event rate and bandwidth. The trigger menu must reflect the physics goals for a given data collection period, taking into account the instantaneous luminosity of the LHC and limitations from the ATLAS detector readout, online processing farm, and offline storage. This document discusses the operation of the ATLAS trigger system during the nominal proton-proton data collection in Run 2 with examples of special data-taking runs. Aspects of software validation, evolution of the trigger selection algorithms during Run 2, monitoring of the trigger system and data quality as well as trigger configuration are presented.
