Abstract
To maintain sensitivity to new physics in the coming years of Large Hadron Collider (LHC) operations, A Toroidal LHC ApparatuS (ATLAS) collaboration has been working on upgrading a portion of the front-end (FE) electronics and replacing some parts of the detector with new devices that can operate under the much harsher background conditions of future LHC runs. The legacy FE of the ATLAS detector sent data to the data acquisition (DAQ) system via the so-called Read Out Drivers (RODs) custom-made VMEbus boards devoted to data processing, configuration, and control. The data were then received by the Read Out System (ROS), which was responsible for buffering them during the High-Level Trigger (HLT) processing. From Run 3 onward, all new trigger and detector systems will be read out using new components, replacing the combination of the ROD and the ROS. This new path will feature an application called the Software Read Out Driver (SW ROD), which will run on a commodity server receiving FE data via the Front-End Link eXchange (FELIX) system. The SW ROD will perform event fragment building and buffering as well as serving the data on request to the HLT. The SW ROD application has been designed as a highly customizable high-performance framework providing support for detector-specific event building and data processing algorithms. The implementation that will be used for Run 3 of the LHC is capable of building event fragments at a rate of 100 kHz from an input stream consisting of up to 120 MHz of individual data packets. This document will cover the design and the implementation of the SW ROD application and will present the results of performance measurements executed on the server models selected to host SW ROD applications during Run 3.
Highlights
SW Readout Drivers (RODs) Components: Default Implementations. These implementations are provided in the form of a shared library that is loaded by the Software Readout Driver (SW ROD) application at run-time
The solution employed by the SW ROD is to assemble input chunks in the data receiving threads
– Netio is a FELIX software network communication protocol built on top of Remote Direct Memory Access (RDMA)
Summary
ATLAS TDAQ system evolution has been mainly driven by the evolution of LHC performance The current system still copes with updated requirements:. It will require a major upgrade of the ATLAS TDAQ system:. Readout Drivers (RODs) provide interface between Front-End (FE) and DAQ:. – Transfer data to the High-Level Trigger (HLT) farm via a commodity switched network. – Transfers data from detector FrontEnd electronics to the new Data Handler component of the DAQ system via a commodity switched network. A new component, known as the Software Readout Driver (SW ROD) has been developed:. A custom PCIe board with Gen 3 x 16 interface installed into a commodity computer:. 12 links at full speed or 24 links with 50% occupancy multiple logical sub-links
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
