Using the DAQ for debugging
Steps from a bare login
- Create a new text/terminal window using the "Paw on a terminal" icon in the start panel.
- In the terminal window, cd ~/src/HTBDAQ .
- To start the DAQ, bin/runDAQ.csh hcalpeds.xml.
- In the same area, or another desktop, start the GUI by clicking on the
GUI icon (screen with wavy traces).
Doing a run
- Change any desired parameters (and check them!) in the "Details..." window.
- Hit INIT
- If the initialization is successful, hit RUN. The DAQ should run
and eventually stop. [at this point all the modules will return to a STOP/OK state]
- If the initialization is not successful, look below for debugging tips.
- If the run was successful, proceed to data plotting.
Plotting the data
- Create another text/terminal window.
- Start ROOT : root
- Load the data access library [ once per ROOT session ] : .L ~/lib/libHTBDAQ_Data.so
- Your data should be available as "/data/tmp/HTB_[your run number].root"
- To run a ROOT script: .x [path to the script, as below]
Some useful ROOT scripts
- ~/src/HTBDAQ/tools/checkCAPIDs.C("filename") -- verify CAPIDs in the file.
- ~/src/HTBDAQ/tools/dumpHCAL.C("filename") -- dump the data from the DCC to the screen
- ~/src/HTBDAQ/tools/plotPedsPerCapid.C("filename",HTR#,Input#) -- plot the pedestals for a given HTR and HTR input (1-24).
Debugging
The best thing to try is to kill the DAQ (^C) and the GUI, and restart both.
This may be required if the DCC gets confused.