The ATLAS high level trigger steering

The High Level Trigger (HLT) of the ATLAS experiment at the Large Hadron Collider receives events which pass the LVL1 trigger at ∼75 kHz and has to reduce the rate to ∼200 Hz while retaining the most interesting physics. It is a software trigger and performs the reduction in two stages: the LVL2 tri...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:Journal of Physics: Conference Series 2008-07, Vol.119 (2), p.022013
Hauptverfasser: Berger, N, Bold, T, Eifert, T, Fischer, G, George, S, Haller, J, Hoecker, A, Masik, J, Nedden, M Z, Reale, V P, Risler, C, Schiavi, C, Stelzer, J, Wu, X
Format: Artikel
Sprache:eng
Schlagworte:
Online-Zugang:Volltext bestellen
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
Beschreibung
Zusammenfassung:The High Level Trigger (HLT) of the ATLAS experiment at the Large Hadron Collider receives events which pass the LVL1 trigger at ∼75 kHz and has to reduce the rate to ∼200 Hz while retaining the most interesting physics. It is a software trigger and performs the reduction in two stages: the LVL2 trigger and the Event Filter (EF). At the heart of the HLT is the Steering software. To minimise processing time and data transfers it implements the novel event selection strategies of seeded, step-wise reconstruction and early rejection. The HLT is seeded by regions of interest identified at LVL1. These and the static configuration determine which algorithms are run to reconstruct event data and test the validity of trigger signatures. The decision to reject the event or continue is based on the valid signatures, taking into account pre-scale and pass-through. After the EF, event classification tags are assigned for streaming purposes. Several new features for commissioning and operation have been added: comprehensive monitoring is now built in to the framework; for validation and debugging, reconstructed data can be written out; the steering is integrated with the new configuration (presented separately), and topological and global triggers have been added. This paper will present details of the final design and its implementation, the principles behind it, and the requirements and constraints it is subject to. The experience gained from technical runs with realistic trigger menus will be described.
ISSN:1742-6596
1742-6588
1742-6596
DOI:10.1088/1742-6596/119/2/022013