Running DAQ Interface » History » Version 30
Running DAQ Interface¶
DAQ Interface is designed to be run, along with rest of the run control code, on lbne35t-gateway01.fnal.gov, using the lbnedaq account. It is located at /data/lbnedaq/scratch/DAQInterface/lbnerc; please note that as this is an active development area you should be aware that code may change and that other users may be working with the package. To get started, first setup the environment:
cd /data/lbnedaq/scratch/DAQInterface source fireup
This will take you into the /data/lbnedaq/scratch/DAQInterface/lbnerc directory. It's a good idea to check whether lbnecontrol (the run control application) and/or DAQInterface (the component which intermediates between run control and artdaq processes) are already running; if they are, the instructions below won't work. To check this, you can try:
ps -A | grep lbnecontrol ps -A | grep daqinterface
If these processes are running, it either means that someone else is using DAQInterface, or that someone else who's done with DAQInterface forgot to clean up. Please use your best judgement, then, before killing these processes.
Assuming the processes aren't running, before getting started, take a look at the configuration file, found in docs/config.txt (relative to /data/lbnedaq/scratch/DAQInterface/lbnerc). It should look something like the following:
lbne-artdaq: /data/lbnedaq/rce/build_lbne-artdaq PMT host: lbnedaq3 log directory: /data/lbnedaq/daqlogs BoardReader host: lbnedaq2 BoardReader port: 5205 BoardReader fhicl: /data/lbnedaq/fcl/BoardReader_TPC_lbnedaq2_1.fcl BoardReader host: lbnedaq2 BoardReader port: 5206 BoardReader fhicl: /data/lbnedaq/fcl/BoardReader_TPC_lbnedaq2_2.fcl EventBuilder host: lbnedaq3 EventBuilder port: 5235 EventBuilder fhicl: /data/lbnedaq/fcl/EventBuilder_lbnedaq2_1.fcl EventBuilder host: lbnedaq3 EventBuilder port: 5236 EventBuilder fhicl: /data/lbnedaq/fcl/EventBuilder_lbnedaq2_2.fcl Aggregator host: lbnedaq2 Aggregator port: 5265 Aggregator fhicl: /data/lbnedaq/fcl/Aggregator_lbnedaq2_1.fcl Aggregator host: lbnedaq2 Aggregator port: 5266 Aggregator fhicl: /data/lbnedaq/fcl/Aggregator_lbnedaq2_2.fcl
The first three parameters allow the user to set the directory in which the desired build of lbne-artdaq to use is located, the host on which artdaq's process management tool script (pmt.rb, used by DAQInterface to launch and kill the artdaq processes) will run, and the directory to which log output will be sent. After this, every cluster of three lines allows one to define an artdaq process; each line should either contain "BoardReader", "EventBuilder" or "Aggregator", defining the process type, and every cluster of three lines should have the same process type. The three lines let one define the host and port of the artdaq process, as well as the FHiCL document which will be used to initialize it. Best practice is to place those FHiCL documents in the /data/lbnedaq/fcl directory. Please note that the order of processes matters, and that they should be listed front-end to back-end, i.e., BoardReader definitions should appear before EventBuilders should appear before Aggregators.
Once you have the configuration file written to your specifications, you can then start run control and DAQInterface:
lbnecontrol & daqinterface -n daqint -r 5570 -c localhost -H localhost &
Here, the "daqint" argument is arbitrary, and is the name you'll give the DAQInterface process; the "5570" argument is the port off of which DAQInterface will run.
Now, you can take DAQ Interface through the standard transitions. At all stages, you can use the "lbnecmd check" command to see what state DAQInterface is in; note that you'll want to wait for a transition to complete before issuing another one, otherwise you'll receive a warning and the transition request will be ignored.
First, take DAQInterface from the "stopped" to the "ready" state; this will create the artdaq processes on the hosts you specified, and initialize them with the FHiCL documents you specified:
lbnecmd init daq
Take DAQInterface from the "ready" to the "running" state, in order to begin datataking:
lbnecmd start daq
Halt the running of the DAQ, returning DAQInterface to the "ready" state from the "running" state:
lbnecmd stop daq
Now, return to the "stopped" state, killing all the artdaq processes:
lbnecmd terminate daq
- Error handling
As of this writing (7/14/14) there has not yet been extensive user feedback concerning DAQInterface; despite this, certain potential problems have been anticipated and are handled within DAQInterface. These problems include:
- An artdaq process returns an error state after a transition request, or an exception is thrown by the XML-RPC library during the request
- During periodic checks, one or more artdaq processes expected to exist are not found
In either case, an error is reported via 0MQ to run control, and the "Recover" transition is automatically triggered. This transition is a fairly blunt instrument: it will kill any remaining artdaq processes and return DAQInterface to its original state of "stopped" (i.e., one in which it requires the "init" transition before anything else is done).
In order to see this for yourself, you can deliberately sabotage one of the transitions. E.g., you can replace one of these filenames listed in the config.txt file with one of your own files intentionally designed to be improper FHiCL; this will then trigger a "recover" transition automatically when an "init" transition is requested. The same thing will occur if you use the name of a file which doesn't exist. After the "recover" transition, you can then use the "lbnecmd check" command to see for yourself that DAQ Interface has returned to its original state. Note that currently, if recover sees that the artdaq processes don't exist, it will raise an exception, which will in turn trigger DAQInterface to end itself.
Please note that if you issue an "init" transition and then follow it with a "terminate" transition, you'll see an exception in the artdaq terminal window which looks like the snippet below; this is because statistics collection which occurs during termination will fail if no data's been collected, which is expected:
Tue Jul 08 14:16:33 -0500 2014: Time Summary: Tue Jul 08 14:16:33 -0500 2014: Min: 0 Tue Jul 08 14:16:33 -0500 2014: Max: 0 Tue Jul 08 14:16:33 -0500 2014: Avg: inf Tue Jul 08 14:16:33 -0500 2014: %MSG-s ArtException: Aggregator-lbnedaqtest01-5265 JobSetup Tue Jul 08 14:16:33 -0500 2014: cet::exception caught in art Tue Jul 08 14:16:33 -0500 2014: ---- DataCorruption BEGIN Tue Jul 08 14:16:33 -0500 2014: NetMonInputDetail: Could not receive message! Tue Jul 08 14:16:33 -0500 2014: ---- DataCorruption END Tue Jul 08 14:16:33 -0500 2014: %MSG Tue Jul 08 14:16:33 -0500 2014: %MSG-s ArtException: Aggregator-lbnedaqtest01-5266 JobSetup Tue Jul 08 14:16:33 -0500 2014: cet::exception caught in art Tue Jul 08 14:16:33 -0500 2014: ---- DataCorruption BEGIN Tue Jul 08 14:16:33 -0500 2014: NetMonInputDetail: Could not receive message! Tue Jul 08 14:16:33 -0500 2014: ---- DataCorruption END
- Your change to daqinterface.py doesn't seem to do anything
Make sure you kill the existing daqinterface process and restart it
- On the initial transition ("lbnecmd init daq"), you see "error: [Errno 111] Connection refused"
If a "Recover" is triggered and you can see via "lbnecmd check" that DAQInterface is in the "stopped" state, try initializing again. If that doesn't work, you can try increasing the value of the pauseBeforeCommands member variable in the DAQInterface class; this is the pause, in seconds, between when the artdaq processes are launched and when they're sent the FHiCL documents to initialize. Empirically, it appears there needs to be a pause of at least 4 seconds on lbnedaqtest01.fnal.gov before the FHiCL documents can be successfully sent via XML-RPC to the processes; increasing this value may make it less likely that the "Connection refused" error occurs. Remember to kill and then restart DAQInterface if you've altered its source code.
- Your change to daqinterface.py doesn't seem to do anything