Abstract
The ATLAS experiment, which records the results of LHC proton-proton collisions, is upgrading its Trigger and Data Acquisition (TDAQ) system during the current LHC first long shutdown. The purpose of this upgrade is to add robustness and flexibility to the selection and the conveyance of the physics data, simplify the maintenance of the infrastructure, exploit new technologies and, overall, make ATLAS data-taking capable of dealing with increasing event rates.While the TDAQ system successfully operated well beyond the original design goals, the accumulated experience stimulated interest to explore possible evolutions. With higher luminosities, the required number and complexity of Level-1 triggers will increase in order to satisfy the physics goals of ATLAS, while keeping the total Level-1 rates at or below 100kHz. The Central Trigger Processor will be upgraded to increase the number ofmanageable inputs and accommodate additional hardware for improved performance, and a new Topological Processor will be included. A single homogeneous high level trigger system will be deployed. The current second and third trigger levels will be executed together on a unique hardware node. This design has many advantages: the radical simplification of the architecture, the flexible and automatically balanced distribution of the computing resources, the sharing of code and services on nodes.In this paper, we report on the design and the development status of the upgraded TDAQ system, with particular attention to the tests currently on-going to identify the required performance and to spot its possible limitations.
Highlights
ATLAS Trigger and Data Acquisition (TDAQ) system in 2012 LHC after the Long Shutdown I (LSI) new challenges for TDAQ
switches and links to ReadOut System New network architecture validated during new data flow software tests
Core chassis equipped with new Brocade 24-port 10 Gbps blade
Summary
More readout channels Level 1 rate: 100 kHz (was 70 kHz in 2012) Average storage rate: 1 kHz (was 700 Hz in 2012). Nominal: 1.5 MB Peak up to ~1.7 MB in 2012 First extrapolation: event size ~2.3 MB at m~80
Published Version (
Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have