2020
DOI: 10.1088/1748-0221/15/10/p10004
|View full text |Cite
|
Sign up to set email alerts
|

Operation of the ATLAS trigger system in Run 2

Abstract: 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 protonproton running, approximately 1500 individual event selections were included in a trigge… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
26
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 68 publications
(26 citation statements)
references
References 49 publications
0
26
0
Order By: Relevance
“…Interesting collision events are selected using a two-level trigger system [17,18,32]. The L1 trigger processes events at a rate of 40 MHz, set by the LHC beam structure consisting of bunches separated by 25 ns.…”
Section: L1 Muon Barrel Triggermentioning
confidence: 99%
“…Interesting collision events are selected using a two-level trigger system [17,18,32]. The L1 trigger processes events at a rate of 40 MHz, set by the LHC beam structure consisting of bunches separated by 25 ns.…”
Section: L1 Muon Barrel Triggermentioning
confidence: 99%
“…Events are selected using a two-stage trigger system which is described in detail in Refs. [15,16]. The first-level (L1) trigger system uses coarse-granularity signals from the calorimeters and the muon system with a 2.5 μs fixed latency and accepts events from the 40 MHz bunch crossings at a rate below 100 kHz.…”
Section: Atlas Detector and Trigger Systemmentioning
confidence: 99%
“…The cause of this was found to be that the performance of the algorithm used to determine the hard-scatter primary-vertex position depended on the nominal online beamspot position (the centre of the region where the two proton bunches cross in the detector). The nominal beamspot position is estimated online by averaging the primary-vertex position over many events [19]. The track reconstruction in the trigger uses the nominal online beamspot position while the online primary-vertex position is defined relative to the detector origin, (x = 0, y = 0, z = 0).…”
Section: Datasets and Simulated Eventsmentioning
confidence: 99%
“…Triggering in ATLAS in Run 2 and Run 3 Takuya Nobe and rate estimation framework described in Ref. [5]. In this framework, trigger rate, CPU usage and the data-flow over DAQ network can be estimated using pp data.…”
Section: Pos(lhcp2021)168mentioning
confidence: 99%