Cargando…

The ATLAS Run-2 Trigger Menu

The ATLAS experiment aims at recording about 1 kHz of physics collisions, starting with an LHC design bunch crossing rate of 40 MHz. To reduce the significant background rate while maintaining a high selection efficiency for rare physics events (such as beyond the Standard Model physics), a two-leve...

Descripción completa

Detalles Bibliográficos
Autores principales: Russell, Heather Lynn, ATLAS Collaboration
Lenguaje:eng
Publicado: 2019
Materias:
Acceso en línea:http://cds.cern.ch/record/2684461
_version_ 1780963323951448064
author Russell, Heather Lynn
ATLAS Collaboration
author_facet Russell, Heather Lynn
ATLAS Collaboration
author_sort Russell, Heather Lynn
collection CERN
description The ATLAS experiment aims at recording about 1 kHz of physics collisions, starting with an LHC design bunch crossing rate of 40 MHz. To reduce the significant background rate while maintaining a high selection efficiency for rare physics events (such as beyond the Standard Model physics), a two-level trigger system is used. Events are selected based on physics signatures such as the presence of energetic leptons, photons, jets or large missing energy. The trigger system exploits topological information, as well as multivariate methods to carry out the necessary physics filtering for the many analyses that are pursued by the ATLAS community. In total, the ATLAS online selection consists of around 1500 individual triggers. A Trigger Menu is the compilation of these triggers, it specifies the physics selection algorithms to be used during data taking, and the rate and bandwidth a given trigger is allocated. Trigger menus must reflect the physics goals for a given run, and also must take into consideration the instantaneous luminosity of the LHC and limitations from the ATLAS detector readout and offline processing farm. For the 2017-2018 run, the ATLAS trigger has been enhanced to be able to handle higher instantaneous luminosities and to ensure the selection robustness against higher average multiple interactions per bunch crossing. We will describe the design criteria for the trigger menu for Run 2. We discuss several aspects of the process of planning the trigger menu, starting from how ATLAS physics goals and the need for detector performance measurements enter the menu design, and how rate, bandwidth, and CPU constraints are folded in during the compilation of the menu. We present the tools that allow us to predict and optimize the trigger rates and CPU consumption for the anticipated LHC luminosities. We outline the online system that we implemented to monitor deviations from the individual trigger target rates, and to quickly react to the changing LHC conditions and data taking scenarios. Finally, we give an overview of the 2015-2018 Trigger Menu and performance, allowing the audience to get a taste of the broad physics program that the trigger is supporting.
id cern-2684461
institution Organización Europea para la Investigación Nuclear
language eng
publishDate 2019
record_format invenio
spelling cern-26844612019-09-30T06:29:59Zhttp://cds.cern.ch/record/2684461engRussell, Heather LynnATLAS CollaborationThe ATLAS Run-2 Trigger MenuParticle Physics - ExperimentThe ATLAS experiment aims at recording about 1 kHz of physics collisions, starting with an LHC design bunch crossing rate of 40 MHz. To reduce the significant background rate while maintaining a high selection efficiency for rare physics events (such as beyond the Standard Model physics), a two-level trigger system is used. Events are selected based on physics signatures such as the presence of energetic leptons, photons, jets or large missing energy. The trigger system exploits topological information, as well as multivariate methods to carry out the necessary physics filtering for the many analyses that are pursued by the ATLAS community. In total, the ATLAS online selection consists of around 1500 individual triggers. A Trigger Menu is the compilation of these triggers, it specifies the physics selection algorithms to be used during data taking, and the rate and bandwidth a given trigger is allocated. Trigger menus must reflect the physics goals for a given run, and also must take into consideration the instantaneous luminosity of the LHC and limitations from the ATLAS detector readout and offline processing farm. For the 2017-2018 run, the ATLAS trigger has been enhanced to be able to handle higher instantaneous luminosities and to ensure the selection robustness against higher average multiple interactions per bunch crossing. We will describe the design criteria for the trigger menu for Run 2. We discuss several aspects of the process of planning the trigger menu, starting from how ATLAS physics goals and the need for detector performance measurements enter the menu design, and how rate, bandwidth, and CPU constraints are folded in during the compilation of the menu. We present the tools that allow us to predict and optimize the trigger rates and CPU consumption for the anticipated LHC luminosities. We outline the online system that we implemented to monitor deviations from the individual trigger target rates, and to quickly react to the changing LHC conditions and data taking scenarios. Finally, we give an overview of the 2015-2018 Trigger Menu and performance, allowing the audience to get a taste of the broad physics program that the trigger is supporting.ATL-DAQ-SLIDE-2019-501oai:cds.cern.ch:26844612019-07-31
spellingShingle Particle Physics - Experiment
Russell, Heather Lynn
ATLAS Collaboration
The ATLAS Run-2 Trigger Menu
title The ATLAS Run-2 Trigger Menu
title_full The ATLAS Run-2 Trigger Menu
title_fullStr The ATLAS Run-2 Trigger Menu
title_full_unstemmed The ATLAS Run-2 Trigger Menu
title_short The ATLAS Run-2 Trigger Menu
title_sort atlas run-2 trigger menu
topic Particle Physics - Experiment
url http://cds.cern.ch/record/2684461
work_keys_str_mv AT russellheatherlynn theatlasrun2triggermenu
AT atlascollaboration theatlasrun2triggermenu
AT russellheatherlynn atlasrun2triggermenu
AT atlascollaboration atlasrun2triggermenu