Using the Online Monitor

Useful Links

Useful People

  • Antonino Sergi
  • Aidan Reynolds
  • James Pillow

Introduction to the OM

The online monitoring (OM) software is designed to run on the raw data files acquired from the DAQ. The OM passes the data output through a number of raw decoders, produces various plots and histograms through art analysers, and then displays the results on the online monitor, Monet.

The OM software should automatically start whenever the run controls are started. If you find this is not the case, refer to the section below.

The software

The OM software can be accessed from any of the np04 servers, and is installed in two places:
  • Production version - /nfs/sw/om/ProtoDUNE_OM_artdaq_v3_02_prod
  • Development version - /nfs/sw/om/ProtoDUNE_OM_artdaq_v3_02_dev
DO NOT edit code found in these directories. It is not possible to push updates to the repos from the np04 servers, and so any code modifications you make are liable to be lost if things go wrong. It is also incredibly annoying for the person trying to pull updates from the repository, as they then need to deal with the versioning conflicts you have caused. Any and all code alterations should be done in your own personal version of the branches used for the OM. Once you have pushed your changes, the np04 dev version will need to pull them, and be rebuilt. These branches and repositories are:

Repository Branch/Version
dunetpc feature/online_monitoring_artdaq_s65_forkv06_73_00
dune_raw_data feature/online_monitoring_artdaq_v3_02
lbne_raw_data feature/online_monitoring_artdaq_v3_02
artdaq_utilities feature/online_monitoring_artdaq_v3_02
artdaq feature/pdune_from_v3_02_00a
artdaq_core v3_02_01

If you want a script that will build you your own version of the OM, then look here.


Foreword - Some things about Monet are quite annoying. Please appreciate its limitations. Some of this is also liable to change, so if you notice something new on Monet, check back here for an updated brief.

When you first click on the Monet link above, you will be presented with the webpage below. If you just click the "DUNE Online" button, it will take you to Monet.

Once in Monet, you will most likely see a blank page like:

Navigating Monet

To navigate Monet, there are two areas of interest to you.

Top Bar

The first area of interest is the right hand side of the top bar.
This thin green bar at the top of the page contains a number of buttons, and a single entry field. The entry field is used to selected the run you wish to view the plots for, and should auto fill with the most recent run when you open Monet.

There are 3 levels of granularity for selecting histogram data with this box:

  1. Run Number
  2. Raw data file number
  3. Histogram file number
these are specified in the run number entry field as numbers separated by dots, i.e. [run number].[raw data number].[hist number], and finer granularity can always be ommited.

Determining "Magic" Navigation Numbers

The most effective way to determine these numbers is to look in the directory /nfs/OMoutput/OMoutput on np04-srv-001. Doing ls -lhtr here will list the most recent files, the three first numbers after np04_hist_run correspond to these three numbers.

Using this entry field comes with a few caveats:

  • Entering a non-existant run number. The page will load without apparent issue, and the entry field will still display the number you entered, however, Monet will automatically load the plots for the most recent run.
  • Not all raw data files are processed by the online monitoring, so an invalid raw data file number will return the most recent run.
  • Leaving the field blank. If you leave the field blank and click 'Go', Monet will load the most recent run. However, the entry field will remain unfilled and this warning will appear (which you can ignore) - fileName.png.

As a result of these caveats it is always worth checking the Rendering info box after requesting a specific run, section below.

On the top bar, you will also notice a 'Reference' button. This will toggle reference plots on and off, allowing you to compare the current run to nominal results. This button currently does not work! We expect to have reference plots within a few weeks of the high voltage being turned on.

Side Bar

The second area of interest is the menu on the left hand side of the page.
This menu is organised by various folders, indicated by the folderClose.png icon when closed, and the folder.png icon when open. Plots found in these folders are indicated by the plot.png icon.

This menu is scrollable, but the scroll bar is only visible when scrolling, so be aware that folders and plots could be hidden past the 'Loading alarms'.

Viewing the Plots

As an example, we will open 'General', located under 'By APA/DSDaS (APA 4)/TPC/'. This will result in a page with two plots. genPlotSmall.png

At the top right of this page, below the green top bar, you will notice some new buttons have appeared: renderInfo.png
The important button for now, is 'Rendering Info'. If you click this, a small context window will appear below it:

This window tells you exactly which file Monet is using to display the plots. It is always a good idea to check this whenever you open Monet, or change the run number, to ensure you are looking at the run number that Monet claims you are.

Beam Monitoring

In the top bar of Monet, use the current run number with ".0" on the development version ( to see the beam monitoring plots.

e.g. run number = 4127.0

OM Output

Raw data files

The raw data files produced by the DAQ are saved in /data0 /data3 on np04-srv-001 np04-srv-004. The have the form np04_raw_runX_Y_dlZ.root, where 'X' is the run number, 'Y' the subrun number, and 'Z' the event builder number.

Histogram files

The histogram files will also be stored in /scratch/OMoutput/ alongside the log files. These files will have the form np04_hist_runN_W_X_Y_Z.root, where 'N' is the run number, W is the raw data file number, X is the histogram file number, and 'Y', 'Z' will indicate which process and partition the raw data file was processed on.


Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng TopBar.png r2 r1 manage 10.6 K 2018-08-31 - 09:29 JamesBryanEdgarPillow  
PNGpng fileName.png r1 manage 7.7 K 2018-08-21 - 11:22 JamesBryanEdgarPillow  
PNGpng folder.png r1 manage 3.7 K 2018-08-21 - 10:00 JamesBryanEdgarPillow  
PNGpng folderClosed.png r1 manage 3.5 K 2018-08-21 - 10:08 JamesBryanEdgarPillow  
PNGpng genPlotSmall.png r1 manage 185.1 K 2018-08-21 - 10:09 JamesBryanEdgarPillow  
PNGpng plot.png r1 manage 3.4 K 2018-08-21 - 10:00 JamesBryanEdgarPillow  
PNGpng postWelcomeSmall.png r1 manage 123.2 K 2018-08-21 - 09:40 JamesBryanEdgarPillow  
PNGpng renderInfo.png r1 manage 11.0 K 2018-08-21 - 14:15 JamesBryanEdgarPillow  
PNGpng renderInfoWindow.png r1 manage 27.7 K 2018-08-21 - 14:40 JamesBryanEdgarPillow  
PNGpng sideBar.png r1 manage 118.0 K 2018-08-21 - 11:33 JamesBryanEdgarPillow  
PNGpng welcomePage.png r1 manage 88.5 K 2018-08-21 - 09:13 JamesBryanEdgarPillow  
PNGpng welcomePageSmall.png r1 manage 73.7 K 2018-08-21 - 09:38 JamesBryanEdgarPillow  
Edit | Attach | Watch | Print version | History: r25 < r24 < r23 < r22 < r21 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r25 - 2018-10-01 - AidanLewisReynolds
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CENF All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback