The data-logging system of the trigger and data acquisition for the ATLAS experiment at CERN

Andreas Battaglia,Szymon Gadomski,Kostas Kordas,Marc Dobson,Hans Peter Beck,Wainer Vandelli

doi:10.1109/nssmic.2007.4436385

Andreas Battaglia, Szymon Gadomski + Show 4 more

Open Access

https://doi.org/10.1109/nssmic.2007.4436385

Copy DOI

Abstract

The ATLAS experiment is getting ready to observe collisions between protons at a centre of mass energy of 14 TeV. These will be the highest energy collisions in a controlled environment to-date, to be provided by the Large Hadron Collider at CERN by mid 2008. The ATLAS Trigger and Data Acquisition (TDAQ) system selects events online in a three level trigger system in order to keep those events promising to unveil new physics at a budgeted rate of ~200 Hz for an event size of ~1.5 MB. This corresponds to a reduction of O(10 <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">5</sup> ) from the initial bunch-crossing rate of 40 MHz at nominal operating conditions. This paper focuses on the data-logging system on the TDAQ side, the so-called "Sub-Farm Output" (SFO) system. It takes data from the Event Filter farm, which is the third level trigger, and it streams and indexes the events into different files, according to each event's trigger path. The data files are moved to CASTOR, the central mass storage facility at CERN. The final TDAQ data-logging system has been installed using 6 Linux PCs, holding 24 disks of 500 GB each, managed by three RAID controllers on each PC. The data-writing is managed in a controlled round-robin way among three independent filesystems associated to a distinct set of disks, managed by a distinct RAID controller. This design allows fast I/O, which together with a high speed network permits to minimize the number of SFO nodes. We report here on the functionality and performance requirements on the system, our experience with commissioning it and on the performance achieved,

Highlights

25 February 2008Abstract—The ATLAS experiment is getting ready to observe collisions between protons at a centre of mass energy of 14 TeV
T HE ATLAS Trigger and Data Acquisition (TDAQ) system is based on three levels of online event selection [1], [2], [3]
The LVL2 trigger reduces the event rate further down to ∼3 kHz based on a selection using the full detector granularity information inside a small region in pseudorapidity-azimuth coordinates around the trigger objects identified by the LVL1 trigger

Summary

25 February 2008

Abstract—The ATLAS experiment is getting ready to observe collisions between protons at a centre of mass energy of 14 TeV These will be the highest energy collisions in a controlled environment to-date, to be provided by the Large Hadron Collider at CERN by mid 2008. The ATLAS Trigger and Data Acquisition (TDAQ) system selects events online in a three level trigger system in order to keep those events promising to unveil new physics at a budgeted rate of ∼200 Hz for an event size of ∼1.5 MB. The data-writing is managed in a controlled round-robin way among three independent filesystems associated to a distinct set of disks, managed by a distinct RAID controller This design allows fast I/O, which together with a high speed network permits to minimize the number of SFO nodes. We report here on the functionality and performance requirements on the system, our experience with commissioning it and on the performance achieved

INTRODUCTION

THE SFO SYSTEM

SFO Hardware

SFO Application

CASTOR client script

MEASUREMENTS

Findings

CONCLUSION