The Readout System for the ITk Pixel Demonstrator for the ATLAS High-Luminosity Upgrade

Buschmann, E.

doi:10.53846/goediss-7996

Cited by 1 publication

(1 citation statement)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As the development of the IBL progressed, both a new readout ASIC, FE-I4 [38], and a new generation of readout systems were introduced and integrated into the EUDAQ framework right from the beginning. In the USBpix Gen2 readout board [39] the incoming data was multiplexed and transmitted by a single Producer, while with the next-generation USBpix Gen3 [40,41] the readout was fully asynchronous using the so-called STcontrol software [42]. Through this tool, data were copied from the DAQ board to the computer and sent by the Producer simultaneously.…”

Section: Atlas Inner Tracker: Pixel Detector Randdmentioning

confidence: 99%

EUDAQ—a data acquisition software framework for common beam telescopes

et al. 2020

View full text Add to dashboard Cite

The development of EUDAQ started as part of the EU-funded Joint Research Activity of the EUDET project "Test Beam Infrastructure" [3,4] in 2005. The goal of the project was the development of a high-precision pixel beam telescope for investigations of the tracking performance of sensor devices. To make this beam telescope a versatile tool for a broad user base and a wide variety of devices, an easy integration strategy for devices under test (DUT) and its DAQ was a priority from the beginning of the project [5]. The interface that was considered to be the most flexible for the user consisted of two separate layers: on the hardware level, the different DAQ systems were to be synchronised using a simple trigger-busy communication protocol; on the software level, the full integration of the DUT into EUDAQ was foreseen as the preferred approach, yet was kept optional.This approach determined the core architecture of EUDAQ [6] which remains today: centralised but distributed core components that communicate with so-called Producers via a custom TCP/IPbased protocol. In this scheme, the latter are responsible for implementing an interface to the individual hardware components, controlling the devices' states and feeding the data into the central data collection unit. Both the beam telescope detector planes and the DUT use the same interface, thus making the framework flexible and independent of any specific hardware. The framework architecture is described in more detail in Section 2.Historically, the most prominent application of EUDAQ is the DAQ of the EUDET-type pixel beam telescopes [7]. They are based on Mimosa26 sensors [8] as telescope planes and a custom-designed trigger logic unit (TLU), the EUDET TLU [9]. Today, the EUDET-type beam telescopes are accessible as common infrastructure at test beam facilities all over the world. This broad availability of beam telescopes combined with the ease-of-use, extensive documentation and user-focus of EUDAQ outlined in Section 3 has led to a large number of successful EUDAQ-based test beam campaigns in the last decade: in Section 4, eleven applications from a wide range of communities are described in more detail.Since the early days of mostly user-driven development, EUDAQ has been moved to a collaborative development model with several active contributors. New features as well as many behind-the-scenes changes such as continuous integration methods paved the road towards the second major version of EUDAQ as briefly outlined in Section 5.

show abstract