Previous Page Main Page What to do while on shift DAQ Trouble Shooting Guide

Updated 2011-12-01

Taking Pedestal Data

To take pedestal data first stop DAQ. This includes:

  1. End the current run by clicking the following buttons in the RC GUI:
    • "End Run"
    • "Release Resources"
      (If at any point this fails, proceed to the next step!)
  2. > (closing all Run Control GUI applications)
  3. > stop System from DAQApplicationManager (stopping all DAQ applications)
    • WAIT until the System is stopped!
  4. To have the last scans result root graphs up (so you can compare to these after your new test) press the "Check DSO Results" icon on NOVA-DAQ-2.

Note that this procedure has changed; please do not reboot the DCMs and, as a consequence, do not re-enable DCS cooling.

After this we are ready to take the pedestal data.

  1. Fill in start_pedestal_run form in the ECL as you start the pedestal run
    • Tag the entry as "DSO/Pedestal Scan"
    • output dir should include day/month/year hour:minute as shown in the pedestal run window).
  2. Locate the "Run Pedestal" icon on the NOVA-DAQ-1 computer (the very left one in the Control Room).
  3. Double-click it.
    After ~ 15 seconds a Pedestal Data Runner application window will appear:
    Pedestal start screen
  4. Press the "Go" button.
  5. After about a minute the progress bars on the DCMs will start moving toward to 100%. It would look something like this:
    Pedestal running screen
  6. Keep an eye on how the pedestal run is processed:
    dcm-3-03-02 and dcm-3-03-03 serve only 2 FEB's and will finish well ahead of the rest, which serve up to 24 (dcm-3-01-01)
    It should take ~ 12 minutes for the run to be finished.
    • During this time the temperatures of the APDs will not be correct on the APD Temperature Monitoring screen.
    • As the scan progresses, individual APDs will light as they are being scanned.
      If at least one DCM behaves not as described, see Troubleshooting section below.
  7. After all DCMs finish the DSO readout (100% everywhere in the status bars, Run Status - "DSO readout finished. Reprocessing in progress"), the data reprocessing starts to produce thresholds, pixel masks, etc.. At this point one can start a normal (DCS) data taking if there is no intention to apply new thresholds and pixel masks. Do not kill PedestalDataRunner, though - let it finish the reprocessing!
  8. After one sees "Run Status" as "DONE", we are done with taking the Pedestal Data.
  9. Close the Pedestal Data Runner window.

Loading New Enable Masks and Thresholds in the Database

The DSO scan will generate a set of FEB and Pixel Masks along with Threholds. Following the scan these values should be checked and, if deemed to look reasonable, loaded into the database prior to the next run. The steps below describe how to both validate the data and load it into the database.

Validate the scan:

  1. From nova-daq-02 launch the Check DSO Results script by double clicking either the "Check DSO Results" or "Check DSO Res vs. DB" icons with a check mark graphic.
  2. Examine the results
    1. If you clicked "Check DSO Res vs. DB", you'll see three canvases. The first is the "current" result of FEB Enable masks, Pixel Enable Masks, and pixel thresholds for the DSO scan just taken. The second is the "reference" result of FEB Enable masks, Pixel Enable Masks, and pixel thresholds currently valid in the database. The last is the difference. For masks, the following color scheme is used to indicate the difference between reference and current:
      Reference  Current   Color 
      On         On         Red
      Off        Off        White
      On         Off        Cyan
      Off        On         Green

      For the thresholds, the arithmetical difference is shown, but only for pixels that are enabled in both reference and current.

      If things look good, proceed.
    2. If you clicked "Check DSO Results", the FEB Enable masks, Pixel Enable Masks, and pixel thresholds for the most recent DSO scan will be displayed on a single canvas.

      Compare these to the previous plots which should have been posted into the logbook -- they should have been tagged as "DSO/Pedestal Scans" so you can search by that.
  3. Post a screen capture of these plots into the logbook. Make sure to tag the entry as "DSO/Pedestal Scans" so the next shifter can find it easily to compare. Save the snapshots to /nova/data/shift/dso so that the files are visible from all control room machines.
  4. Close the plots by selecting "Quit ROOT" from the File dropdown of any of the three plots. (DO NOT close using the x on the terminal window.)
  5. If everthing looks reasonable proceed to load the masks and thresholds.

Loading Masks and Thresholds:

Thresholds and Masks should be loaded from the DAQConfigEditor (launched from ICON on control machine 1)
Click Action -> Load Thresholds and Mask : Follow the prompting.
For now, load the values with exception overrides to duplicate the previous behavior of the script.
Detailed Instructions are available here.

(The command-line loading is still available but should be avoided where possible.)
While logged on ctrl-master as novadaq_
  1. Execute <date string>_
    Example: _
    [novadaq@novadaq-ctrl-master ~]$ 2011-04-12_08_19_18_
    11329 pixels have threshold values defined.
    483 FEBs have pixel masks set.
    11 dcms have FEB masks set
    Press return key to load into database or ctrl-c to abort...
    # If a resonable number of pixels, febs, and dcms are reported. Press enter to finish the load. You see the following lines:
    Loading into nova_prod on at port 5433 ....
    Reading /data/PedestalData/PedScans/2011-04-12_08_19_18/febmask_2011-04-12_08_19_1
    Reading /data/PedestalData/PedScans/2011-04-12_08_19_18/pixelmask_2011-04-12_08_19
    Reading /data/PedestalData/PedScans/2011-04-12_08_19_18/thresholds_2011-04-12_08_1
  2. Once the prompt is returned to you you're finished! The next run should use these latest masks and threshold values.


The pedestal data run lasts for ~ 12 minutes. If it takes much less or much more than that try to
  • Close Pedestal Runner Window
  • Reboot the dcm's by reboot-dcm-all or, if necessary, power-cycle the dcms.
  • Retake pedestal data.

If that still does not help, contact Denis Perevalov. NOvA phone Book

Instructions for experts

Previous Page Main Page What to do while on shift DAQ Trouble Shooting Guide