Speaker
Description
Modern detector systems utilize numerous Front-End Electronics (FEEs). These FEEs can occasionally become unstable, requiring a restart. Furthermore, to improve the signal-to-noise ratio, FEEs are often mounted near the detector, placing them in the vicinity of the beam, where radiation-induced Single Event Upsets (SEUs) can cause malfunctions or shutdowns.
In conventional data acquisition (DAQ) procedures, when an FEE malfunctioned, the common practice was to stop the entire data acquisition, restart the problematic FEE, and then resume DAQ. If FEE malfunctions occur frequently, this procedure results in significant downtime, negatively impacting the statistical precision of the experiment.
To mitigate this, we implement a new procedure: stopping the readout from the troubled FEE, restarting the FEE, and then resuming its readout, all without stopping the overall data acquisition process.
A distributed DAQ system we are developmenting, called NestDAQ, performs data collection through the cooperation of numerous single-function processes. Among these processes, the TimeFrameBuilder (TFB) is responsible for collecting and consolidating data from all FEEs. This process detects FEEs from which data is not arriving and reports the anomaly to an online database. Another process for recovery monitors the database, controls the Sampler process which reads out the problematic FEE, commands it to stop readout, initiates the FEE restart, and controls the FEE's re-entry into the DAQ stream. This mechanism resolves FEE issues without stopping the DAQ, allowing data collection to continue uninterrupted.
We will explain the mechanism and implementation of this partial restart feature on NestDAQ.
| Minioral | Yes |
|---|---|
| IEEE Member | No |
| Are you a student? | No |