Cargando…
The ATLAS Read-Out System Performance with first data and perspective for the future
The Readout System (ROS) is the ATLAS DAQ element that receives the data fragments from the ~1600 detector readout links, buffers them and provides them on demand to the second level trigger processor or to the event building system. The ROS system is implemented with ~150 PCs each one housing in av...
Autores principales: | , , , , , , , , , , , , , , |
---|---|
Lenguaje: | eng |
Publicado: |
2009
|
Materias: | |
Acceso en línea: | http://cds.cern.ch/record/1172412 |
_version_ | 1780916169721511936 |
---|---|
author | Crone, G Della Volpe, D Gorini, B Green, B Joos, M Kieft, G Kordas, K Kugel, A Misiejuk, A Schroer, N Teixeira-Dias, P Tremblet, L Vermeulen, J Wickens, F Werner, P |
author_facet | Crone, G Della Volpe, D Gorini, B Green, B Joos, M Kieft, G Kordas, K Kugel, A Misiejuk, A Schroer, N Teixeira-Dias, P Tremblet, L Vermeulen, J Wickens, F Werner, P |
author_sort | Crone, G |
collection | CERN |
description | The Readout System (ROS) is the ATLAS DAQ element that receives the data fragments from the ~1600 detector readout links, buffers them and provides them on demand to the second level trigger processor or to the event building system. The ROS system is implemented with ~150 PCs each one housing in average 4 custom-built PCI mezzanine boards (ROBIN) and a 4-port PCIe NIC. Each PC runs a multithreaded OO-software framework managing the requests for data coming through the NIC and collecting the corresponding fragments from the physical buffers. At LHC luminosity of 10^33 cm-2s-1, corresponding to an average Level1 trigger rate of 75 kHz, the ROS has to concurrently service up to approximately 20 kHz of data requests from the Level2 trigger and up to 3.5 kHz of requests from event building nodes. The system has been commissioned in 2007 and since then has been working smoothly. For the most of 2008 the main activity has been data taking with cosmics in which the Level1 trigger rate is much lower with respect to LHC operation. However, the commissioning of the detector requires a much larger data size per event and a very limited rate reduction between Level1 and Level2, pushing the ROS to operate in unforeseen conditions. We will describe here the ROS performances under these conditions, analyze them in view of the 2009 data taking conditions and discuss evolutionary scenarios of the ROS system for improving its flexibility and enh ance its performances, especially in view of the super LHC upgrade. |
id | cern-1172412 |
institution | Organización Europea para la Investigación Nuclear |
language | eng |
publishDate | 2009 |
record_format | invenio |
spelling | cern-11724122019-09-30T06:29:59Zhttp://cds.cern.ch/record/1172412engCrone, GDella Volpe, DGorini, BGreen, BJoos, MKieft, GKordas, KKugel, AMisiejuk, ASchroer, NTeixeira-Dias, PTremblet, LVermeulen, JWickens, FWerner, PThe ATLAS Read-Out System Performance with first data and perspective for the futureDetectors and Experimental TechniquesThe Readout System (ROS) is the ATLAS DAQ element that receives the data fragments from the ~1600 detector readout links, buffers them and provides them on demand to the second level trigger processor or to the event building system. The ROS system is implemented with ~150 PCs each one housing in average 4 custom-built PCI mezzanine boards (ROBIN) and a 4-port PCIe NIC. Each PC runs a multithreaded OO-software framework managing the requests for data coming through the NIC and collecting the corresponding fragments from the physical buffers. At LHC luminosity of 10^33 cm-2s-1, corresponding to an average Level1 trigger rate of 75 kHz, the ROS has to concurrently service up to approximately 20 kHz of data requests from the Level2 trigger and up to 3.5 kHz of requests from event building nodes. The system has been commissioned in 2007 and since then has been working smoothly. For the most of 2008 the main activity has been data taking with cosmics in which the Level1 trigger rate is much lower with respect to LHC operation. However, the commissioning of the detector requires a much larger data size per event and a very limited rate reduction between Level1 and Level2, pushing the ROS to operate in unforeseen conditions. We will describe here the ROS performances under these conditions, analyze them in view of the 2009 data taking conditions and discuss evolutionary scenarios of the ROS system for improving its flexibility and enh ance its performances, especially in view of the super LHC upgrade.ATL-DAQ-SLIDE-2009-065ATL-COM-DAQ-2009-024oai:cds.cern.ch:11724122009-03-14 |
spellingShingle | Detectors and Experimental Techniques Crone, G Della Volpe, D Gorini, B Green, B Joos, M Kieft, G Kordas, K Kugel, A Misiejuk, A Schroer, N Teixeira-Dias, P Tremblet, L Vermeulen, J Wickens, F Werner, P The ATLAS Read-Out System Performance with first data and perspective for the future |
title | The ATLAS Read-Out System Performance with first data and perspective for the future |
title_full | The ATLAS Read-Out System Performance with first data and perspective for the future |
title_fullStr | The ATLAS Read-Out System Performance with first data and perspective for the future |
title_full_unstemmed | The ATLAS Read-Out System Performance with first data and perspective for the future |
title_short | The ATLAS Read-Out System Performance with first data and perspective for the future |
title_sort | atlas read-out system performance with first data and perspective for the future |
topic | Detectors and Experimental Techniques |
url | http://cds.cern.ch/record/1172412 |
work_keys_str_mv | AT croneg theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT dellavolped theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT gorinib theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT greenb theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT joosm theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT kieftg theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT kordask theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT kugela theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT misiejuka theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT schroern theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT teixeiradiasp theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT trembletl theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT vermeulenj theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT wickensf theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT wernerp theatlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT croneg atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT dellavolped atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT gorinib atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT greenb atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT joosm atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT kieftg atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT kordask atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT kugela atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT misiejuka atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT schroern atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT teixeiradiasp atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT trembletl atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT vermeulenj atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT wickensf atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture AT wernerp atlasreadoutsystemperformancewithfirstdataandperspectiveforthefuture |