Welcome to the NP04/protoDUNE-SP Online Monitoring TWiki Home page

List of Metrics

Priority:

• Event Display
• Mean and RMS
• FFT
• Check for Stuck Bits
• display of beam region vs non-beam region
• Trigger ?
• Photon Detector ?

Desirable:

• Purity check
• Muon monitors

Online Monitoring on LArSoft

Disclaimer: The source codes were inspired by the work stored in dune35t found in various modules in LArSoft.

• The source code is stored under _/srcs/dunetpc/dune/Protodune/OnlineMonitor and it contains multiple modules:
  • OnlineMonitor_module.cc:
    • the ranges are hardwired --> needs improvements
  • OnlineMonitorWithPedestal_module.cc:
    • --> same as above

• • RawEventDisplay_module.cc
  • FFT_module.cc
  • StuckBits_module.cc
  • PurityAna_module.cc

• Channel Mapping:
  • loop through channels in the first APA to find the channel boundaries for each view
• Filling:
  • loop over all raw digits (entire channels) , look in each view (per chan) for each APA
  • Histos stored for each APA, each View

Simulated Scenarios

The OnlineMonitor metrics are tested and validated under various simulated scenarios. These simulated data are based on following chain: gen (particle ID, input geometry)-> g4 (full MC truth, energy deposits) -> detsim (scintillation light and ionization electrons from energy deposits, recombination of ionization electrons, attenuation of electrons number, due to LAr impurities at given drift distance, longitudinal and transverse diffusion of electrons at given drift distance, added readout info: electronics response, noise, ADC waveforms on readout channels)

Various conditions of the noise were produced (by Dorota and Robert) and they are stored here: http://dune-data.fnal.gov/mc/mcc8/protodune_request1/index.html.

Access and copy of the simulated data

For new people: follow up the instructions at: https://web.fnal.gov/collaboration/DUNE/SitePages/How%20to%20Map%20Your%20CERN%20Grid%20Cert%20to%20GUMS%20at%20FNAL.aspx

For those who have already certificate installed and want to copy from fermilab to neutplatform - example to use copy from http://dune-data.fnal.gov/mc/mcc8/protodune_request1/xml/protoDune/ProtoDUNE_beam_2GeVc_cosmics_3ms_noise_high_detsim.list

• voms-proxy-init --voms dune:/dune/Role=Analysis -vomses ~/dunevomses
• xrdcp xroot://fndca1.fnal.gov/pnfs/fnal.gov/usr/dune/persistent/dunepro/v06_18_01_01/detsim/ProtoDUNE_beam_2GeVc_cosmics_3ms_noise_high/12938753_0/ProtoDUNE_beam_2GeVc_cosmics_3ms_noise_high_0_20161231T120953_detsim2_e28b54c3-cfa2-4b67-81bc-907e32d22d49.root /mnt/nas01/users/radescu/Feb2017_v22/inputs/.

Scenario Description

• standard detsim makes low, white noise, equivalent to 1.6 parameter for white noise in exp.noise version
• desim_noise has exponential noise on top of white, with still reasonable amplitudes
• detsim_noise_high is ~worst case.

• • low noise (using protoDUNE_detsim.fcl)
  • medium noise (using protoDUNE_detsim_noise.fcl)
    

    Medium Noise Scenario
  • high noise - a la dune35t (using protoDUNE_detsim_noise_high.fcl)
    

    Simulated Noise Scenarios

These noise definitions are based on the parameters used for the WhiteNoise (incoherent - flat noise) and for the NoiseNorm parameters (exponential noise). These parameters are defined in .fcl files in srcs/dunetpc/fcl/protodune/detsim/ .

Moreover, since the Online Monitoring aims to address the sanity of the data quality, raw data is simulated with various assumptions of electronics: These flags exist in the default .fcl files: srcs/dunetpc/fcl/protodune/detsim/protoDUNE_detsim.fcl

• physics.producers.daq.NoiseOn:
• physics.producers.daq.PedestalOn:
• physics.producers.daq.DistortOn:
• physics.producers.daq.SuppressOn:

Which correspond to:

• with or without distortion applied
• with or without Suppression applied

Following parameters were used for these conditions if applied:

Performance monitoring via profiling tool

A first attempt to monitor the profiling was performed used igprof tool. It has the advantage that it does not require re-configuration and it should work with the default LArSoft optimisation. This is now installed centrally on the neut platform cluster. To use it just run a setup:

• • source /mnt/nas01/software/products/setups
  • setup igprof v5_9_16 -q e10

However, the demangle does not really work and then it’s hard to digest the performance

• - for performance:

• • igprof -d -pp -t lar -o igprof_lar.pp.gz lar -c ..
  • igprof-analyse -d -v -g igprof_lar.pp.gz > igreport_perf.res

• - for memory:

• • igprof -d -mp -t lar -o igprof_lar.gz lar -c ...
  • igprof-analyse -d -v -g -r MEM_TOTAL igprof_lar.gz > igreport_total.res

Output Root Files

The working platform for the online monitor is now on the daq machine: pddaq-gen05.

Location

The files will be stored there: /daq/onlinemonitor/data_histos/simulation .

Convention

The name convention of files is run_#_ev_#_time_#.root The time # is ...

The test outputs are stored for now in the public lxplus area till Marco settles his accounts on neutrino cluster:

• ~radescu/public/forMarco/

Web Tool Monitor (Marco)

Back to protoDUNE-SP Data Quality Twiki Main Page

Back to protoDUNE-SP Data Preparation Twiki Main Page

---

Major updates:

-- NectarB - 2017-03-02 - created web site

-- VoicaAnaMariaRadescu - 2017-03-16 - created structure and content