The original requirements for DQM were published as DocDB 1811. Over time, there was more detail added to some of the DQM components and their expected functionality.
As an additional piece of information, it is useful to consider "uBooNE lessons learned" information (courtesy M.Mooney)
- Electron lifetime/purity every 2-8 hours. Hardware and software. Track-based, requires O(1000) triggers.
- Noise filtering + event display is important (that's on the protoDUNE DQM list)
- Removal of coherent noise allows for uncovering of more subtle problems
- Channel "health": pedestal RMS, channel FFTs
- Slow Control is critical. Mostly for HV monitoring
- Drill down from global view to subsystems
- Space Charge Effect probably not needed in DQM
Evolution of the DQM plan
See DocDB references for prompt processing, p3s etc (cf. DocDB 1861). The short list of DQM items includes
- ADC/FFT with variety of aggregation modes (e.g. APA, board, power supply etc)
- signal processing (filtering, de-noising, deconvolution etc)
- some (unspecified) fast recontruction and event display
Early 2017: additions by Flavio et al. Need to monitor BI itself and also match tracks to the TPC.
Comments and questions:
- pLAPPD ToF will be joined with the “normal” DAQ data stream
- The fiber tracker data, other spill-relevant data, and ckov data will go into the BI DB
- When and how to capture BI data from the DB? (Current thinking from J.Paley - purely offline, from CERN DB without own cache - any news on that?)
- When and how to merge it with the TPC and other data?
- Track reco and matching to the TPC - who will do it?
Signal Processing and Basic Event Display
Mid-2017: add basic event-display-type (cf. channel vs time) of visual product before and after signal processing.
- demonstrates that the detector and software both work
- similar to the original paper
- BNL team has plans for this item, leveraging signal processing experience in μBooNE, 35t etc
- Synergy with the OM group
* prototypes such as “purity calculation” have been tested under p3s at CERN - thousands of jobs run * the boundary between OM and DQM can be quite fluid, most software is portable * ROOT and art/LArSoft are common denominators * Photon Detector (need more info) * CRT will need to be merged offline (need more info)