Project

General

Profile

Running on the pdunedaq cluster at Fermilab

In one terminal:

-Log in to pdunedaq01 as dunedaq
-Execute the following

cd daqarea
. fireup
kill_daq_applications.sh -d

You might see either or both of the following; don't be concerned if this is the case:
Killing DAQInterface
WARNING in /home/nfs/dunedaq/daqarea/bin/kill_daq_applications.sh: unable to find available DAQInterface to kill
Killing tee
WARNING in /home/nfs/dunedaq/daqarea/bin/kill_daq_applications.sh: unable to find available tee to kill

Then, execute
launch_daq_applications.sh -d docs/config.txt

and hit enter when you see
DAQInterface launched; if running DAQInterface in the background, can press <enter> to return to shell prompt

Now,
 cd sdaqinterface_scripts
python ~/artdaq-utilities-sdaqinterface/rundaq.py 

And you'll start to see
SDAQ_STATUS:Existing

appear every second or so. Then type the following three commands:
init
boot
config

The first two are no-ops and will execute almost immediately. The third will call the traditional 35ton "lbnecmd init daq"; you'll want to wait until you see something like the following before issuing any further commands:
Tue Nov 15 13:08:36 CST 2016: Initialize transition complete; if running DAQInterface in the background, can press <enter> to return to shell prompt

Then,
run

and the DAQ will run, using a single ToySimulator instance. To wrap things up, do the following:
stop
terminate

where before typing "terminate", you'll want to wait for a message like the following:
Tue Nov 15 13:11:37 CST 2016: Stop transition complete for run 125; if running DAQInterface in the background, can press <enter> to return to shell prompt

Now we can look at the output. Create a temporary directory somewhere (called <tmp> below), and type the following:
. ~/daqarea/bin/setup_conftool
cd <tmp>
conftool.sh -o export_global_config -g demo1R<run_number>

where <run_number> is provided, among other places, in the "Stop transition complete" message. You should see the following:
Return status: succeed

Then, from <tmp>, you can see the FHiCL documents you used to initialize the artdaq processes (and which were saved in the database) by looking in newconfig/<run_number>/ . Also saved are FHiCL-ized versions of the DAQInterface configuration file and the run metadata file.

You can also see the configuration in the output root file itself. Look for the most recent root file in /tmp (not to be confused with <tmp>, above) and execute the following:

config_dumper -P /tmp/<rootfilename> | sed -r 's/\\n/\n/g' 

where <rootfilename> denotes the root file produced during the run.