FD DAQ General and Backend & Computing Requirements Kurt Biery, Giles Barr, Josh Klein FD DAQ Design Workshop 30-Oct-2017
Full DAQ Requirements (docdb 112) • For nonbeam data, a DUNE far detector module shall adopt a data acquisition strategy suitable for the DUNE SNB physics capabilities. • A DUNE far detector module shall transmit continuously digitized channel waveforms to the DAQ at an appropriate sampling frequency. • A DUNE far detector module shall provide the continuously digitized channel waveforms at a frequency that optimizes both the charge resolution and determination of closely spaced tracks. • A DUNE far detector module shall collect events with visible energy of >100 MeV with no dead time • For events with visible energy < 100 MeV, a DUNE far detector module shall optimize the energy resolution over the detection efficiency. • A DUNE far detector module shall have the ability to trigger at the time of the beam pulse regardless of the presence of a beam interaction in the module. • A DUNE far detector module shall be able to contribute data into a unified event that includes data from all active modules for offline analysis. 2 30-Oct-2017 Kurt Biery | DAQ Back-End & Computing
Full DAQ Requirements (docdb 112) • The TPC, photon detector, electronics, and DAQ shall be designed to allow testing in surface facilities and laboratories before transporting underground. • The far detector shall measure event times with high efficiency such that for events with visible energy above 200 MeV the drift coordinate can be measured with sufficient precision. • For beamline events, the far detector shall measure the absolute time of the event with accuracy sufficient to correlate it with the beam spill. • The far detector shall measure the event time for events with visible energy <200 MeV with high efficiency and sufficient precision to correct for drift time and improve energy resolution. • The far detector shall measure absolute event time with sufficient accuracy to allow global analysis of a supernova neutrino wave front. 3 30-Oct-2017 Kurt Biery | DAQ Back-End & Computing
Full DAQ Requirements (docdb 112) • The FD Data Acquisition shall assemble data from all active modules into a unified event for offline analysis. • The FD data acquisition systems shall allow control and monitoring during detector operations. • The FD data acquisition shall be integrated into the global DAQ for LBNF/DUNE. • The FD data acquisition shall have the capability of notifying the world-wide science community of an astronomical event in a timely way. • LBNF/DUNE shall have a Global Data-Acquisition (DAQ) system capable of collection and readout of all needed experimental data (from beam systems, near, far detectors) to attain the primary objectives of the Long-Baseline Neutrino Facility and Deep Underground Neutrino Experiment. • The far detector TPC shall be configured so that continuous data taking can be performed even if some fraction of the detector is not operational. 4 30-Oct-2017 Kurt Biery | DAQ Back-End & Computing
High Level / System Requirements (1) Flexibility • Commercial networking and software processing would allow us to respond to changes in the required rates and rejection factors “Software” compression, noise filtering, zero-suppression, event filtering • Could include co-processors, but the let’s say software- driven for starters • Software processing before event assembly? Software triggering? 5 30-Oct-2017 Kurt Biery | DAQ Back-End & Computing
High Level / System Requirements (2) Requirements driven by physical considerations • Limitations on power or cooling underground • Underground and above-ground disk buffer? • Whatever steps are needed for hand-off to offline? 6 30-Oct-2017 Kurt Biery | DAQ Back-End & Computing
High Level / System Requirements (3) Provide data transfer; event assembly Provide necessary data throughput; disk-writing rates, disk buffer Control and DAQ monitoring Real-time data quality monitoring Graceful handling and communication of back-pressure Provide necessary elements for downstream data management Partitioning Provide necessary uptime, reliability, startup & restart times 7 30-Oct-2017 Kurt Biery | DAQ Back-End & Computing
Requirements for various components Run Control • Graphical, scriptable, command-line variant? • Pick system components • Pick configuration • Minimal set of user-visible states while still allowing fast turn around when needed. DQM • Parasitic to primary data flow (crashes do not affect). • Support for monitoring-application-specific trigger type, rate, etc. requests? • Is there a need to see all events? • Web-based displays? World or VPN/VNC viewable Etc, etc. 8 30-Oct-2017 Kurt Biery | DAQ Back-End & Computing
Backup Slides 9 30-Oct-2017 Kurt Biery | DAQ Back-End & Computing
Computing System First-pass-reference (FPR) design: • Commercial servers and components • Size of system varies based on architecture choices Computing ¡System 10 30-Oct-2017 Kurt Biery | DAQ Back-End & Computing
Run Control & Data Management Online ¡software ¡in ¡green; ¡Run ¡Control ¡Software ¡in ¡blue 11 30-Oct-2017 Kurt Biery | DAQ Back-End & Computing
Recommend
More recommend
![T i n k e r [ T e c h ] PORTFOLIO BACKEND N o d e . j s , D j a n g o ,](https://c.sambuz.com/643717/t-i-n-k-e-r-t-e-c-h-s.jpg)
