Monitoring the Data¶
Link to Nearline Monitoring:
How to Interpret the Nearline Frontage Plots Test Beam¶
This page is designed to explain to you what the nearline front page plots should look like and cover the main failure modes that you are likely to see in each plot and how to recover from them.
Temporary conditions may cause features to be present. Always read the shift bulletin board for the latest running conditions announcements.
- First note the timestamp on the bottom left corner of the plot. This should be within the last 15 minutes. If this is not the case, then this indicates that the web-plot making scripts aren't running.
- The new data appears on the right edge of the plot. There might be a small (20 minute) gap of white space between the most recent data and the right edge of the plot as it takes awhile for the plots to update. If there is a lot of white space on the right side of the plot and the detector is on with a run going, then this is an indication that the nearline processing has stopped.
- If you see either of these issues, email email@example.com.
Average DDActivity Trigger Rate¶
This plot shows the rate of the DDActivity trigger averaged per subrun over the last day. When beam is on, the rate should be around 18-20 Hz. With beam off, the rate is around 14 Hz.
Our DAQ has an issue that causes the trigger rates to drop off for an unknown reason. If the DDActivity trigger rate drops below 10 Hz, this plot will turn red. If this plot is red, call your DAQ expert so they can restart the run.
Average Beamline Trigger Rate¶
This plot shows the rate of the Beamline trigger seen by the detector averaged per subrun over the last day. When beam is on, the rate should be around 0.01-0.03 Hz. If the rate is 0 and you know beam is on, call your DAQ expert so they can diagnose the problem (most likely the Beamline DAQ needs restarting).
Number of Active FEBs per Subrun¶
This plot shows the number of FEBs that report any hits in a subrun.
The dashed green line represents the total possible FEBs that could be active (126 for Test Beam).
The Test Beam TDU occasionally disconnects, causing the auto-enable DAQ to stop working. If the number of active FEBs drops below 122, this plot will turn red. If this plot is red, call your DAQ expert so they can reconnect the TDU.
FEB Hit Rate Spectra vs. Time¶
This plot shows the rate of hits in the detector per subrun. The rate will vary with beam conditions. Keep an eye out for any FEBs with a much higher or lower rate than average.