Artículo
Operation of the ATLAS trigger system in Run 2
Fecha
2020-10Registro en:
Journal of Instrumentation, Volume 15, Issue 10 October 2020 Article number P10004
1748-0221
DOI: 10.1088/1748-0221/15/10/P10004
Autor
Aad, G.
Abbott, B.
Abbott, D.C.
Abed, Abud A.
Abeling, K.
Abhayasinghe, D.K.
Abidi, S.H.
AbouZeid, O.S.
Abraham, N.L.
Abramowicz, H.
Abreu, H.
Abreu, R.
Abulaiti, Y.
Acharya, B.S.
Achkar, B.
Adam, L.
Adam, Bourdarios C.
Adamczyk, L.
Adamek, L.
Adelman, J.
Adersberger, M.
Adiguzel, A.
Adorni, S.
Adye, T.
Affolder, A.A.
Afik, Y.
Agapopoulou, C.
Agaras, M.N.
Aggarwal, A.
Agheorghiesei, C.
Aguilar-Saavedra, J.A.
Ahmad, A.
Ahmadov, F.
Ahmed, W.S.
Ai, X.
Aielli, G.
Akatsuka, S.
Akbiyik, M.
Åkesson, T.P.A.
Akilli, E.
Akimov, A.V.
Al Khoury, K.
Alberghi, G.L.
Albert, J.
Alconada Verzini, M.J.
Alderweireldt, S.
Aleksa, M.
Aleksandrov, I.N.
Alexa, C.
Alexopoulos, T.
Alfonsi, A.
Alfonsi, F.
Alhroob, M.
Ali, B.
Ali, S.
Aliev, M.
Alimonti, G.
Allaire, C.
Allbrooke, B.M.M.
Allen, B.W.
Institución
Resumen
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