Running DAQ Interface » History » Version 190

John Freeman, 10/10/2015 06:32 PM

1 58 John Freeman
2 58 John Freeman
3 96 John Freeman
4 96 John Freeman
5 49 Erik Blaufuss
h1. Getting help
6 1 John Freeman
7 78 John Freeman
If, after reading this document (in particular, the "Troubleshooting and FAQ" section) you run into issues, or have questions, please contact:
8 49 Erik Blaufuss
* DAQInterface
9 49 Erik Blaufuss
** John Freeman -
10 62 John Freeman
* RunControl
11 49 Erik Blaufuss
** Erik Blaufuss -
12 66 John Freeman
* Configuration Manager
13 1 John Freeman
** Jon Paley -
14 123 John Freeman
* TDU XML-RPC server
15 123 John Freeman
** Tom Dealtry -
16 1 John Freeman
17 102 Erik Blaufuss
h1. Logbook
18 102 Erik Blaufuss
19 102 Erik Blaufuss
Please document all changes, software updates, and operational activities to the ELog:
20 102 Erik Blaufuss
21 102 Erik Blaufuss
22 120 John Freeman
23 1 John Freeman
h1. Brief preliminaries
24 1 John Freeman
25 189 John Freeman
Everything in this wiki was up-to-date as of October 11, 2015.
26 189 John Freeman
27 136 John Freeman
This guide assumes you have access to the lbnedaq account on the LBNE 35 ton gateway node, . It also assumes you have a rudimentary knowledge of how to navigate a bash environment in Linux (how to change directories, log onto different machines, perform time-ordered listings of files, edit a file using emacs or vi, etc.). 
28 49 Erik Blaufuss
29 188 John Freeman
The installed code is located at If you need access to the lbnedaq account, please contact one of the people listed above under "Getting Help". Once you have access, to get started, login (<code>ssh -l lbnedaq</code>) and first setup the environment:
30 1 John Freeman
31 1 John Freeman
32 1 John Freeman
cd /data/lbnedaq/daqarea
33 1 John Freeman
source fireup
34 189 John Freeman
35 1 John Freeman
36 1 John Freeman
This will take you into the /data/lbnedaq/daqarea/lbnerc directory, out of which the DAQ is controlled. For the remainder of this wiki, the assumption is that you've already setup the environment using the above commands. 
37 1 John Freeman
38 188 John Freeman
Keep in mind that you shouldn't run the DAQ if someone else is using it. To figure out whether this is the case, see "Getting the status", further down this document. Also keep in mind that when you use the DAQ, you should make a note of it in the elog, along with how long you plan to use it and whether you're willing to let someone else step in if you're work is non-urgent.  A reminder to this effect is printed whenever you log into 
39 1 John Freeman
40 188 John Freeman
To see the terminal output of RunControl and DAQInterface, you'll want to be in the same terminal from where they were launched. This means it's typically not a good idea to try to use a "stale" RunControl and/or DAQInterface that someone else may have started hours (or even days) ago. 
41 188 John Freeman
42 188 John Freeman
Concerning example output shown in this document:  when you see an ellipse ("…"), that is to be interpreted as a placeholder for output which is considered irrelevant to the point being explained.
43 188 John Freeman
44 123 John Freeman
h1. Killing, launching, and getting the status of the DAQ applications
45 123 John Freeman
46 123 John Freeman
The DAQ application suite consists of RunControl, the configuration manager, DAQInterface (the component which intermediates between RunControl, the configuration manager, and the artdaq processes) and the XML-RPC server for the TDU (the program which allows a sync pulse to be sent to the hardware at the start of DAQ running). The following points about these programs should be observed:
47 123 John Freeman
** These applications all need to be running in order for the DAQ to work
48 188 John Freeman
** DAQInterface needs to be launched _after_ RunControl
49 1 John Freeman
** The actual names of the processes are "lbnecontrol" (RunControl), "daqinterface" (DAQInterface), "CfgMgrApp" (the configuration manager) and "tdu" (the TDU XML-RPC server)
50 1 John Freeman
51 167 John Freeman
h2. Getting the status
52 167 John Freeman
53 165 John Freeman
In order to determine which DAQ applications are already active, two approaches can be taken, depending on whether or not RunControl is itself active. If it isn't, you'll need to enter the following:
54 1 John Freeman
55 1 John Freeman
56 165 John Freeman
57 165 John Freeman
58 176 John Freeman
which will produce output which looks like this:
59 1 John Freeman
60 176 John Freeman
61 188 John Freeman
lbnecontrol: **Not Found**
62 188 John Freeman
CfgMgr: Available
63 176 John Freeman
DAQInterface: Available
64 176 John Freeman
TDUControl: **Not Found**
65 176 John Freeman
66 176 John Freeman
Most recent DAQ logfile written (current US Central Time is Apr 10 09:56):
67 176 John Freeman
Apr 8 17:25 /data/lbnedaq/daqlogs/pmt/pmt-32342.1-20150408171225.log
68 155 John Freeman
69 1 John Freeman
70 188 John Freeman
In other words, the above command will both tell you which, if any, of the four primary DAQ applications are running, and then tell you the time of the most recently modified logfile; this last piece of information is helpful in determining whether the DAQ is currently in active use by another individual. In particular, you see that the configuration manager and DAQInterface already exist, but RunControl and the TDU's XML-RPC server do not. In this case, you would not only want to launch RunControl and the server, but you would also want to kill and relaunch DAQInterface. Unless someone had just posted in the elog that they were planning to run on the DAQ (and did so before you had a chance to post!), you wouldn't need to worry about interfering with someone else's DAQ work, since you can see above that it's been almost two days since any DAQ output was logged. 
71 155 John Freeman
72 176 John Freeman
Another way of checking which applications are alive is through "@lbnecmd check@"; note this command will only work if RunControl (lbnecontrol) is itself alive:
73 1 John Freeman
74 1 John Freeman
lbnecmd check
75 1 John Freeman
76 138 John Freeman
77 176 John Freeman
You'll then see output similar to that of as far as which applications are alive; however, it contains additional information not shown which will be discussed later:
78 124 John Freeman
79 124 John Freeman
lbnecontrol: Available
80 124 John Freeman
CfgMgr: **Not Found**
81 1 John Freeman
DAQInterface: Available
82 124 John Freeman
TDUControl: **Not Found**
83 1 John Freeman
84 1 John Freeman
85 91 John Freeman
86 176 John Freeman
Be aware that if you attempt "lbnecmd check" when RunControl is not yet available, you'll simply see "<code>check failed: '[Errno 111] Connection refused'.  Is lbnecontrol running?</code>".
87 49 Erik Blaufuss
88 124 John Freeman
h2. Cleanup: killing RunControl, DAQInterface, the configuration manager, and the TDU XMLRPC server
89 1 John Freeman
90 152 John Freeman
As of March 30, 2015, a new script called "" can be run at the command line to kill the DAQ applications. In order to kill all four applications, one would run:
91 152 John Freeman
92 152 John Freeman
93 152 John Freeman -c -d -r -t
94 152 John Freeman
95 152 John Freeman
96 160 John Freeman
where each option corresponds to the killing of a particular application: "-c" for the configuration manager, "-d" for DAQInterface, "-r" for RunControl, and "-t" for the TDU XML-RPC server. If only a subset of these four applications are running, then only use the relevant options (e.g., simply run "<code> -t</code>" if the only application running is the TDU server). Running the script without any options at all will print out instructions similar to what you see here. Be aware that it's good etiquette to make sure someone's not currently using the DAQ before you start killing applications. 
97 152 John Freeman
98 153 John Freeman
For the previous instructions for killing the applications (still correct, though more work-intensive), click on "Show", below:
99 152 John Freeman
100 152 John Freeman
101 152 John Freeman
102 124 John Freeman
Killing RunControl has its own special syntax, and is simply:
103 1 John Freeman
104 109 Thomas Dealtry
105 124 John Freeman
lbnecmd kill
106 1 John Freeman
107 105 John Freeman
108 124 John Freeman
The other DAQ applications, however, need to be killed via the standard Linux command <code>kill <pid></code>, where "<pid>" is the process ID of the application. To find the process IDs of all possible DAQ applications, you can run:
109 105 John Freeman
110 105 John Freeman
111 124 John Freeman
ps aux | grep -v grep | grep -v emacs | egrep -e lbnecontrol -e daqinterface -e CfgMgrApp -e tdu
112 105 John Freeman
113 1 John Freeman
114 140 John Freeman
For each application which exists, a row will appear, the second field of which is that application's process ID. Keep in mind, of course, that if these processes are running, it might mean that someone else is using the DAQ. As the 9th and 10th fields of the row of variables "ps aux" returns concern how long the program has been running, you can use these values as well as your best judgement, then, before deciding these processes are not in active use and killing them.
115 152 John Freeman
116 105 John Freeman
117 124 John Freeman
h2. Launching RunControl, DAQInterface, the configuration manager, and the TDU XMLRPC server
118 105 John Freeman
119 154 John Freeman
Also as of March 30, 2015, a new script called "" can be run at the command line to launch the DAQ applications. In order to launch all four applications, one would run:
120 154 John Freeman
121 154 John Freeman -c -t -r -d <daqinterface configuration file>
122 154 John Freeman
123 154 John Freeman
124 161 John Freeman
where unless you have your own working copy of the DAQInterface configuration file (what this is will be described later in this wiki), "<code><daqinterface configuration file></code>" should be "<code>docs/config.txt</code>". The options refer to the same applications as in the case of, and like, executing the script without any options will print out instructions. Be aware, however, that DAQInterface will not be launched if RunControl isn't already running. In practice, though, you can launch RunControl in the same command by preceding the DAQInterface option with the RunControl option -- so, if the configuration manager and the TDU server are already up and available, then one would only need to execute "<code> -r -d <daqinterface configuration file></code>" in order to have the full suite of DAQ applications available for use. 
125 154 John Freeman
126 154 John Freeman
Note that if an application of a given type is already running, will not launch a duplicate application, but will instead print a warning to the screen. 
127 154 John Freeman
128 190 John Freeman
Note also that when you launch DAQInterface, a window with the header "MessageFacility MsgViewer" will pop up; it's in this window that messages about the running DAQ (color coded by severity level) will appear. More on this in a bit. 
129 190 John Freeman
130 161 John Freeman
For the previous instructions on how to launch the DAQ applications (still correct, but more detailed and labor-demanding), click on "Show" below:
131 154 John Freeman
132 154 John Freeman
133 154 John Freeman
134 181 John Freeman
_Old instructions for launching RunControl_
135 49 Erik Blaufuss
136 124 John Freeman
137 49 Erik Blaufuss
rm -f /tmp/  # (This should only be necessary if last RunControl session wasn't killed via "lbnecmd kill")
138 1 John Freeman
lbnecmd launch
139 1 John Freeman
140 61 John Freeman
141 181 John Freeman
_Old instructions for launching DAQInterface_
142 151 John Freeman
143 151 John Freeman
144 151 John Freeman
daqinterface -f <daqinterface file> &
145 151 John Freeman
146 1 John Freeman
147 1 John Freeman
The "-f <daqinterface file>" is optional; if left out, the lbnerc/docs/config.txt file will be used to configure DAQInterface, otherwise <daqinterface file> will be used. The DAQInterface configuration is not to be confused with run configurations handled by the configuration manager; see the section "The DAQInterface configuration file" for more. 
148 1 John Freeman
149 154 John Freeman
Other "expert" arguments:
150 151 John Freeman
151 1 John Freeman
daqinterface -n daqint -r 5570 -c localhost -H localhost -f <daqinterface file> &
152 1 John Freeman
153 1 John Freeman
Here, the "daqint" argument is arbitrary, and is the name you'll give the DAQInterface process in RunControl; the "5570" argument is the port off of which DAQInterface will run.  "-c" refers to the host on which RunControl is running, and "-H" the host on which DAQInterface is running. 
154 141 John Freeman
155 154 John Freeman
156 154 John Freeman
If multiple users with different terminals wish to check the DAQ output, it is recommended to try:
157 1 John Freeman
158 82 John Freeman
stdbuf -oL daqinterface -n daqint -r 5570 -c localhost -H localhost -f <daqinterface file> >>~/DI.log 2>&1 &
159 1 John Freeman
160 1 John Freeman
This will launch daqinterface in the background, with all messages being appended to the bottom of the file ~/DI.log  (The stdbuf -oL prevents buffering of output to the file, so the file should update in real time)
161 141 John Freeman
162 154 John Freeman
163 181 John Freeman
_Old instructions for launching the configuration manager_
164 1 John Freeman
165 1 John Freeman
Please see the "Starting up the CfgMgrApp on lbne35t-gateway01" section of Jon Paley's documentation here:
166 109 Thomas Dealtry
167 181 John Freeman
_Old instructions for launching the TDU XMLRPC server_
168 109 Thomas Dealtry
169 109 Thomas Dealtry
170 124 John Freeman
tdu -T -P 10001 -H localhost -r 50008 &
171 1 John Freeman
172 1 John Freeman
173 109 Thomas Dealtry
?Note that if you are using emulators, you don't need to run using the TDU. Remember to set 'TDU XMLRPC port' to less than or equal 0.
174 125 John Freeman
175 154 John Freeman
See [[Starting and using TDUControl]] for more details.
176 1 John Freeman
177 154 John Freeman
178 62 John Freeman
179 162 John Freeman
h1. Performing a Run
180 1 John Freeman
181 142 John Freeman
With the applications launched, you can take the DAQ system through the standard transitions to perform a DAQ run. The "ground state" of the DAQ is called the "stopped" state. Each successful transition brings the DAQ into a different state.  Described in more detail later, the chain of states (in quotes) and transitions (in italics) in the DAQ system can be represented as follows:
182 1 John Freeman
183 142 John Freeman
184 143 John Freeman
185 188 John Freeman
"stopped" -> _init_ -> "ready" -> _start_ -> "running" -> _pause_ -> "paused" -> _resume_ -> "running" -> _stop_ -> "ready" -> _terminate_ -> "stopped"
186 143 John Freeman
187 142 John Freeman
188 142 John Freeman
189 125 John Freeman
h2. Checking the state of the DAQ
190 127 John Freeman
191 125 John Freeman
At all stages, you can use the "lbnecmd check" command to see what state DAQInterface is in; example output of this is as follows:
192 1 John Freeman
193 125 John Freeman
lbnecontrol: Available
194 125 John Freeman
CfgMgr: Available
195 125 John Freeman
DAQInterface: Available
196 125 John Freeman
TDUControl: Available
197 125 John Freeman
198 125 John Freeman
Run number: 797
199 125 John Freeman
Run configuration: ganglia_test
200 125 John Freeman
Run type: Test
201 125 John Freeman
daqint@localhost:5570 (synchronous): running
202 125 John Freeman
203 125 John Freeman
204 125 John Freeman
Here, you've already seen how lbnecmd check can tell you whether a given application type has been launched or not; on the bottom line, however, you'll also see a description of the _state_ of the DAQ -- in this case, "running", meaning that it's actively acquiring data. 
205 108 John Freeman
206 108 John Freeman
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. DAQInterface will also report when transitions are complete -- e.g., at the end of the "initialize" transition, you'd see:
207 117 John Freeman
208 108 John Freeman
Initialize transition complete; if running DAQInterface in the background, can press <enter> to return to shell prompt
209 1 John Freeman
210 142 John Freeman
If a high "debug level" has been set for DAQInterface (see below for more on this), this message can get buried in a set of output messages; in this case "lbnecmd check" may be the easiest way to determine what state the system is in.
211 1 John Freeman
212 94 John Freeman
h2.  Selecting a run configuration and DAQ components
213 49 Erik Blaufuss
214 125 John Freeman
*Before initializing or starting a DAQ run*, a configuration and set of DAQ components must be selected.  This is done via RunControl.
215 1 John Freeman
216 49 Erik Blaufuss
h3. List and select a configuration:
217 1 John Freeman
218 62 John Freeman
To see the list of available configurations (queried from the configuration manager):
219 49 Erik Blaufuss
220 1 John Freeman
lbnecmd listconfigs
221 1 John Freeman
222 143 John Freeman
This lists all available configs, as well as the current selected config (Note, default config is "No Config"):
223 1 John Freeman
224 1 John Freeman
Available configs (Name : description)
225 1 John Freeman
226 189 John Freeman
rces_and_ssps : Run up to 8 SSPs and 4 RCEs, with ganglia, online monitoring, and root file output enabled
227 189 John Freeman
228 189 John Freeman
demo_rc_reporter : A version of the demo which reports metrics to RunControl
229 189 John Freeman
230 111 John Freeman
demo : This is a demo.  Testing 1, 2, 3…
231 30 John Freeman
232 1 John Freeman
233 49 Erik Blaufuss
Current selected config: No Config
234 1 John Freeman
235 49 Erik Blaufuss
You can then select a configuration -- for the purposes of this tutorial, let's go with "demo", which creates simulated data without using any hardware:
236 1 John Freeman
237 1 John Freeman
lbnecmd setconfig demo
238 1 John Freeman
239 189 John Freeman
This will return "OK" if successful; "lbnecmd listconfigs" will then show this as the current config via its last line of output: <code>Current selected config: demo</code>.  If the specified configuration is not known, an error is returned. Instructions on how to add or edit a configuration (an expert-only action) are given later in this document.
240 1 John Freeman
241 189 John Freeman
Note: when taking data with the machine, you'll most likely be using the "rces_and_ssps" configuration; this allows you to connect to the SSPs, RCEs and Penn trigger board, runs the online monitoring module, and saves the output data in *.root files. 
242 189 John Freeman
243 49 Erik Blaufuss
h3. List and select DAQ components.
244 1 John Freeman
245 189 John Freeman
You can select which portions of the LBNE DAQ setup you want to use in the upcoming run.  These are mapped generally to the artdaq BoardReaderMain processes
246 189 John Freeman
that read them out. As an operator, you need to ensure that there are configuration files available in the configuration manager for the DAQ Components that you select here, or DAQInterface will return an error- so, for example, if you're using the "demo" configuration, you couldn't request ssp01 as one of the components, since the demo configuration only allows for components which create simulated (i.e., fake) data. 
247 1 John Freeman
248 49 Erik Blaufuss
To see the list of available DAQ components:
249 1 John Freeman
250 49 Erik Blaufuss
lbnecmd listdaqcomps
251 62 John Freeman
252 1 John Freeman
Will return a list of components available and selected (*Default* is ALL available components), e.g.:
253 112 John Freeman
254 112 John Freeman
255 112 John Freeman
component01 (lbnedaq2:5205)
256 112 John Freeman
component02 (lbnedaq2:5206)
257 112 John Freeman
258 112 John Freeman
ssp08 (lbnedaq1:5214)
259 112 John Freeman
260 112 John Freeman
261 112 John Freeman
component01 (lbnedaq2:5205)
262 112 John Freeman
component02 (lbnedaq2:5206)
263 1 John Freeman
264 1 John Freeman
ssp08 (lbnedaq1:5214)
265 62 John Freeman
266 143 John Freeman
The components are shown by name, along with the requested host/port to run the component's corresponding BoardReaderMain process on. You can then select a list of DAQ components to use in the run:
267 1 John Freeman
268 1 John Freeman
lbnecmd setdaqcomps component0{1,2}
269 118 John Freeman
270 49 Erik Blaufuss
(n.b. the {1,2} in brackets is a Linux bash shell trick which expands <code>component0{1,2}</code> to <code>component01 component02</code>). This will return "OK" if successful ("lbnecmd listdaqcomps" will show this in the "selected" set of components).  If the specified components are not known, an error is returned.
271 143 John Freeman
272 143 John Freeman
How to make a new component available to RunControl is described later in this document. 
273 29 John Freeman
274 91 John Freeman
h2. Initializing, starting, stopping and terminating a Run
275 1 John Freeman
276 66 John Freeman
For each of these transitions, please recall that while "lbnecmd <cmd>" returns very quickly, the actual issued command can take several seconds or minutes to complete.  Before issuing another command, be sure that the transition is complete by using the check command:
277 1 John Freeman
278 49 Erik Blaufuss
lbnecmd check
279 1 John Freeman
280 62 John Freeman
For example, before issuing the "start" transition, you can use this command to ensure that the DAQ is in the "ready" state and not still in the "initializing" stage.
281 1 John Freeman
282 167 John Freeman
First, take DAQInterface from the "stopped" to the "ready" state; this will create the artdaq processes on the hosts they've been assigned, and initialize them with the FHiCL documents:
283 1 John Freeman
284 1 John Freeman
lbnecmd init daq
285 1 John Freeman
286 1 John Freeman
287 190 John Freeman
You'll see the MessageFacility MsgViewer window fill with a few messages; it'll look something like this:
288 190 John Freeman
289 190 John Freeman
290 190 John Freeman
291 190 John Freeman
You'll be able to filter out messages by level of severity; so, for example, if you only cared about Error messages you could click on "Error" in the upper-right hand corner of the window. To reinstate the display of Error, Warning and Info messages, you could click on "Info". In general, allowing for these three types of message is probably a good default. Note that developer decisions about what messages constitute Error vs. Warning vs. Info are still evolving as of Oct 10, 2015, and will likely be influenced by the first couple of weeks of running. 
292 190 John Freeman
293 190 John Freeman
Now, in order to begin taking data, take DAQInterface from the "ready" to the "running" state:
294 179 John Freeman
295 179 John Freeman
lbnecmd start daq
296 179 John Freeman
297 179 John Freeman
Immediately, you'll see a request for a confirmation that the configuration and selected components are in fact the ones you want; it will look something like the following:
298 1 John Freeman
299 1 John Freeman
DAQ config
300 1 John Freeman
301 179 John Freeman
Run Type: Test
302 190 John Freeman
Selected config: demo
303 179 John Freeman
Selected DAQ components:
304 190 John Freeman
   component01 (lbnedaq1:5205)
305 190 John Freeman
   component02 (lbnedaq1:5206)
306 190 John Freeman
Start DAQ with these settings? [y]|n: 
307 179 John Freeman
308 179 John Freeman
Assuming you're happy with the configuration and components, hit "y" to proceed, and as with the other transitions, wait for the "transition complete" message to appear. 
309 186 John Freeman
310 49 Erik Blaufuss
Note that the current run number is displayed when DAQ is in the running state using the "lbnecmd check" command. If the start transition was successful, information about the run is saved in the run records directory, @/data/lbnedaq/run_records/<run_number>@, where @<run_number>@ is to be taken as a stand-in for the actual run number. More on how to understand the directory's contents is described below, under "Examining the output". Of immediate interest, the real-time output of the DAQ will be saved in a logfile located in /data/lbnedaq/daqlogs/pmt/. While in the running state, you can obtain its name just by executing the "" script described above; with its name, if you open up a fresh terminal and run "tail -f <logfilename>" you'll see the logfile updating in real time. Please note that after reaching a predefined number of bytes, the logfile will cease being written to and a new logfile will be opened up; this is the most likely reason that you stop seeing updates after running the "tail -f" command. 
311 178 John Freeman
312 22 John Freeman
Pause the running of the DAQ, putting DAQInterface into the "paused" state.  This will cause the current open output Root file, in /data/lbnedaq/data, to be closed and given a name reflecting the current run and subrun numbers (the format as of April 10, 2015 is @lbne_r<run number>_sr<subrun number>_<creation time>.root@):
313 21 John Freeman
314 42 John Freeman
lbnecmd pause daq
315 41 John Freeman
316 167 John Freeman
317 1 John Freeman
Resume the running of the DAQ, returning it to the "running" state.  This will restart data taking to a new output file:
318 48 John Freeman
319 48 John Freeman
lbnecmd resume daq
320 48 John Freeman
321 48 John Freeman
322 48 John Freeman
Halt the running of the DAQ, returning DAQInterface to the "ready" state from the "running" state:
323 48 John Freeman
324 49 Erik Blaufuss
lbnecmd stop daq
325 49 Erik Blaufuss
326 127 John Freeman
From the ready state, you can start a new run with the same configuration and DAQ components you originally selected. 
327 1 John Freeman
*NOTE* To select a new configuration or DAQ component set, you must issue the "terminate" command, which will kill all ArtDAQ processes and return DAQInterface to its "stopped" state:
328 67 Erik Blaufuss
329 67 Erik Blaufuss
330 67 Erik Blaufuss
lbnecmd terminate daq
331 1 John Freeman
332 172 John Freeman
333 1 John Freeman
h2. Examining the output
334 129 John Freeman
335 119 John Freeman
Once you've completed your run, there are typically two primary outputs: the Root files which contain the data which passed through the DAQ (saved, as of March 25, 2015, in /data/lbnedaq/data on the gateway node), and a set of text files containing information about the run. To access these text files, you'll want to go to the run records directory, which defaults to /data/lbnedaq/run_records/<run_number>. This directory contains the FHiCL documents used to control the ArtDAQ processes in the run, the DAQInterface configuration file used (described later in this wiki), and a metadata file, which, among other things, describes where to find a record of the DAQ's output. An example of this file, for run 778, can be found if we look in /data/lbnedaq/run_records/778 at "metadata_r778.txt":
336 72 John Freeman
337 72 John Freeman
338 72 John Freeman
Config name: demo
339 1 John Freeman
Component #0: component01
340 119 John Freeman
Component #1: component02
341 119 John Freeman
lbne-artdaq commit: 0f0f9be1c63a3b487170579c887ce79944eca6f8
342 119 John Freeman
lbnerc commit: 92935f2702c5e0aa732fd3cc9ff6758e1a0c288c
343 1 John Freeman
/data/lbnedaq/config/ commit: 97d8b222742a41d5d10ea942a063ddfacac3ce93
344 114 John Freeman
345 114 John Freeman
346 1 John Freeman
pmt logfile(s): lbnedaq3:/data/lbnedaq/daqlogs/pmt/pmt-25771*.log
347 1 John Freeman
348 1 John Freeman
boardreader logfiles: 
349 1 John Freeman
350 1 John Freeman
351 1 John Freeman
352 1 John Freeman
eventbuilder logfiles: 
353 1 John Freeman
354 1 John Freeman
355 1 John Freeman
356 1 John Freeman
357 1 John Freeman
aggregator logfiles: 
358 1 John Freeman
359 1 John Freeman
360 1 John Freeman
361 167 John Freeman
362 1 John Freeman
The most significant things saved in this file for the end user of the DAQ system are the configuration chosen and the components chosen for the run (at the top of the file), and the wildcard for the pmt (ArtDAQ Process Management Tool) logfiles, which contain the output of the DAQ system, under "pmt logfile(s)" -- so, in this case, executing <code>ls -ltr /data/lbnedaq/daqlogs/pmt/pmt-25771*.log</code> would list the files containing the output of the DAQ in run 778. Concerning this last point, just be aware of the possibility that earlier DAQ sessions may have produced logfiles which also satisfy the wildcard, as the "25771" in the wildcard example provided refer to the process ID of the pmt process, which isn't necessarily unique for a given run. 
363 119 John Freeman
364 129 John Freeman
365 129 John Freeman
{{collapse(Comprehensive details on the contents of the run records directory...)
366 129 John Freeman
367 129 John Freeman
** The full contents of the metadata file, beyond what's described above, include: 
368 129 John Freeman
-The git commit hashes of the lbne-artdaq and lbnerc packages used in the run, as well as the commit hash of the configuration directory used by the configuration manager
369 129 John Freeman
-The individual artdaq process logfiles
370 129 John Freeman
371 129 John Freeman
** A copy of the DAQInterface configuration file with a name of the format <code>config_r<run number>.txt</code> is saved. A description of what this file is comes later in the wiki. 
372 129 John Freeman
373 129 John Freeman
** Please note that the FHiCL documents saved in the run records directory will contain the actual FHiCL sent to the artdaq processes for the run, and that this will be slightly different than the contents of the FHiCL documents found in the configuration manager's directory. This is because DAQInterface performs some bookkeeping on FHiCL variables which account for things such as the number of processes of a given type (note that it makes no changes which would affect the physics). The saved FHiCL document name is standardized to <processtype>_<host>_<port>_r<run number>.fcl, so, e.g, "EventBuilder_lbnedaq2_5735_r778.fcl" refers to the FhiCL used to control the EventBuilderMain process on lbnedaq2 at port 5735 during run 778. 
374 129 John Freeman
375 129 John Freeman
** Please also note that the entire subdirectory for the configuration is also saved alongside the FHiCL documents; this is because some FHiCL documents are included via "#include" into the main FHiCL documents for a given process, and this was the way to save them as well as the main FHiCL documents. 
376 129 John Freeman
377 129 John Freeman
378 129 John Freeman
379 185 John Freeman
{{collapse(How to examine your output Root files...)
380 76 John Freeman
Various art modules may create various types of output. In particular, it's standard for one of the two AggregatorMains running in an artdaq-based DAQ to use art's RootOutput module, which will save the assembled raw event in an art-readable *.root file. The location of this output can be found in the FHiCL code used to control RootOutput; as of March 30, 2015, the standard location is /data/lbnedaq/data on the gateway node. The other AggregatorMain typically will run other modules designed to create plots, diagnostic printouts, etc.; the nature of the output here is too varied to neatly summarize, but checking the FHiCL code used to control these art modules should reveal their output location.
381 185 John Freeman
382 76 John Freeman
To take a quick look at the art-readable *.root file, with a version of lbne-artdaq newer than 11/25/14, you can do the following:
383 76 John Freeman
384 76 John Freeman
385 76 John Freeman
cd <lbne-artdaq basedir>
386 76 John Freeman
source setupLBNEARTDAQ
387 76 John Freeman
rawEventDump -s <rootfile> -n <max events>
388 76 John Freeman
389 186 John Freeman
390 166 John Freeman
where here, <lbne-artdaq basedir> is the parent directory of the lbne-artdaq package (make sure the package is of a version equal to or higher than the one used to produce the *.root file - you can check the saved metadata*.txt and DAQInterface configuration files in the run_records/ directory for info on this), <rootfile> is the art-readable *.root file produced in a given run, and <max events> is the max events whose info you wish to look at. For a specific example of the output, say we look at the first event of run 731:
391 166 John Freeman
392 166 John Freeman
rawEventDump -s /data/lbnedaq/data/lbne_r000731_sr01_20150317T162037.root -n 1
393 1 John Freeman
394 166 John Freeman
395 166 John Freeman
Then the output will look something like the following:
396 81 John Freeman
397 166 John Freeman
398 81 John Freeman
%MSG-i MF_INIT_OK:  art 08-Apr-2015 13:29:00 CDT JobSetup 
399 81 John Freeman
Messagelogger initialization complete.
400 166 John Freeman
401 1 John Freeman
%MSG-i PathConfiguration:  art 08-Apr-2015 13:29:00 CDT JobSetup 
402 1 John Freeman
Multiple end paths have been combined into one end path,
403 1 John Freeman
"end_path" since order is irrelevant.
404 1 John Freeman
405 166 John Freeman
406 166 John Freeman
08-Apr-2015 13:29:00 CDT  Initiating request to open file /data/lbnedaq/data/lbne_r000731_sr01_20150317T162037.root
407 81 John Freeman
08-Apr-2015 13:29:00 CDT  Successfully opened file /data/lbnedaq/data/lbne_r000731_sr01_20150317T162037.root
408 1 John Freeman
409 166 John Freeman
Package             |Version             |Timestamp           
410 166 John Freeman
artdaq-core         |v1_04_10            |11-Mar-2015 14:35:37 UTC
411 166 John Freeman
artdaq              |v1_12_08            |11-Mar-2015 14:37:50 UTC
412 166 John Freeman
lbne-raw-data       |v1_02_00            |11-Mar-2015 14:36:11 UTC
413 76 John Freeman
lbne-artdaq         |v1_01_02            |13-Mar-2015 20:31:07 UTC
414 166 John Freeman
415 81 John Freeman
Begin processing the 1st record. run: 731 subRun: 1 event: 1 at 08-Apr-2015 13:29:00 CDT
416 166 John Freeman
417 166 John Freeman
DAQ......... | daq........... | PHOTON............... | std::vector<artdaq::Fragment> | artdaq::Fragments.... | ...7
418 81 John Freeman
DAQ......... | daq........... | TPC.................. | std::vector<artdaq::Fragment> | artdaq::Fragments.... | ...8
419 1 John Freeman
DAQAG....... | TriggerResults | ..................... | art::TriggerResults.......... | art::TriggerResults.. | ...-
420 166 John Freeman
421 1 John Freeman
Total products (present, not present): 8 (3, 5).
422 76 John Freeman
423 76 John Freeman
424 1 John Freeman
DAQAG....... | BuildInfo... | LbneArtdaq........... | std::vector<artdaq::PackageBuildInfo> | artdaq::PackageBuildInfos | ...4
425 76 John Freeman
426 81 John Freeman
Total products (present, not present): 1 (1, 0).
427 166 John Freeman
428 1 John Freeman
08-Apr-2015 13:29:00 CDT  Closed file /data/lbnedaq/data/lbne_r000731_sr01_20150317T162037.root
429 76 John Freeman
430 76 John Freeman
TrigReport ---------- Event  Summary ------------
431 76 John Freeman
TrigReport Events total = 1 passed = 1 failed = 0
432 76 John Freeman
433 76 John Freeman
TrigReport ------ Modules in End-Path: end_path ------------
434 76 John Freeman
TrigReport  Trig Bit#    Visited     Passed     Failed      Error Name
435 76 John Freeman
TrigReport     0    0          1          1          0          0 printBuildInfo
436 76 John Freeman
TrigReport     0    0          1          1          0          0 out1
437 76 John Freeman
438 166 John Freeman
TimeReport ---------- Time  Summary ---[sec]----
439 1 John Freeman
TimeReport CPU = 0.017439 Real = 0.007998
440 1 John Freeman
441 166 John Freeman
Art has completed and will exit with status 0.
442 129 John Freeman
443 166 John Freeman
444 131 John Freeman
The first thing you see here is the version and build time of the lbne-artdaq package and some of the main packages on which it depends. Then you see a listing of products in the Root file, here including seven fragments of type PHOTON (from the SSPs) and eight fragments of type TPC (from the RCEs).  Finally, a listing of passed/failed events; the output here is the result of running with "-n 1" as an option, so as we'd expect there's only one event.
445 1 John Freeman
446 145 John Freeman
447 1 John Freeman
h1. The DAQInterface configuration file
448 167 John Freeman
449 100 John Freeman
DAQInterface uses some key information stored in a local configuration file, NOT to be confused with the run configuration described elsewhere on this wiki. Examples of this information are the hosts and ports (i.e., communication sockets) for artdaq processes, location of lbne-artdaq software, debug (log) level, etc). These can be changed while the DAQ is in its "stopped" state. The default DAQInterface configuration file is docs/config.txt (relative to /data/lbnedaq/daqarea/lbnerc); if you wish to change parameters, it's considered best practice not to edit this default file but rather to copy it to a file of the form "<code>docs/config_<your username>.txt</code>", and edit that file, passing it to the DAQInterface executable as described in the section on launching applications. It's expected that for normal operations, most parameters should not need to changed too often, and alterations will be primarily of developer or expert interest. If you ARE a developer/expert or are simply curious, take a look at the default DAQInterface configuration file; it should look something like the following:
450 91 John Freeman
451 1 John Freeman
452 100 John Freeman
lbne-artdaq: /data/lbnedaq/daqarea/lbne-artdaq-base/build_lbne-artdaq
453 1 John Freeman
454 49 Erik Blaufuss
PMT host: lbnedaq3
455 49 Erik Blaufuss
PMT port: 5400
456 49 Erik Blaufuss
457 49 Erik Blaufuss
pause before initialization: 5
458 49 Erik Blaufuss
459 49 Erik Blaufuss
# debug level can range from 0 to 3 (increasing order of verbosity)
460 49 Erik Blaufuss
debug level: 1
461 91 John Freeman
462 49 Erik Blaufuss
log directory:   /data/lbnedaq/daqlogs
463 116 John Freeman
464 116 John Freeman
record directory: /data/lbnedaq/run_records
465 116 John Freeman
466 116 John Freeman
# If this file is "config.txt" -- i.e., the standard, non-expert,
467 101 John Freeman
# non-testing version of the DAQInterface configuration file -- do not
468 101 John Freeman
# set "disable configuration check" to "true"
469 101 John Freeman
470 91 John Freeman
disable configuration check: false
471 167 John Freeman
472 48 John Freeman
TDU XMLRPC port: 50008
473 91 John Freeman
474 91 John Freeman
EventBuilder host: lbnedaq2
475 91 John Freeman
EventBuilder port: 5235
476 48 John Freeman
477 91 John Freeman
EventBuilder host: lbnedaq2
478 91 John Freeman
EventBuilder port: 5236
479 48 John Freeman
480 91 John Freeman
Aggregator host: lbnedaq2
481 1 John Freeman
Aggregator port: 5265
482 1 John Freeman
483 1 John Freeman
Aggregator host: lbnedaq2
484 1 John Freeman
Aggregator port: 5266
485 130 John Freeman
486 1 John Freeman
487 130 John Freeman
488 1 John Freeman
The parameters you're most likely to change will be the following:
489 130 John Freeman
490 130 John Freeman
* *lbne-artdaq* : the directory in which the desired build of lbne-artdaq to use is located; you would change this if you'd modified and built a personal copy of lbne-artdaq for hardware troubleshooting purposes, for example.
491 130 John Freeman
492 130 John Freeman
* *debug level* : allows the user to set the verbosity level of the output to the screen; setting it to higher values creates greater verbosity, and as a practical matter, the range of settings is currently 0-3. Loosely speaking, "0" means minimal output (not much beyond simply announcing a transition is complete), "1" includes announcements of progress during transitions, "2" includes these announcements plus the values of certain variables as well as lbne-artdaq output, and "3" is primarily of developer interest. 
493 130 John Freeman
494 130 John Freeman
* *disable configuration check* : a boolean which can be set to "true" or "false"; normally this should be set to "false", which means that on the start transition, DAQInterface will intentionally fail and put itself into the "stopped" state if it discovers that edits have been made to the configuration directory since the last commit in that directory. If very frequent edits to the configuration directory are made during hardware debugging, however, switching this feature on to "true" can make life considerably easier. 
495 130 John Freeman
496 130 John Freeman
* *TDU XMLRPC port* : the value of the port through which DAQInterface will communicate with an XML-RPC server linked to the TDU. Needed for DAQInterface to send a sync pulse to the TDU at the beginning of the "start" and "resume" transitions. If this is set to 0 or a negative value, no sync pulse is attempted. For more on the TDU and its code, see Tom Dealtry's Wiki "here":
497 1 John Freeman
498 92 John Freeman
{{collapse(Other parameters are as follows…)
499 116 John Freeman
500 93 John Freeman
* *PMT host* : the host on which artdaq's process management tool script (pmt.rb, used by DAQInterface to launch and kill the artdaq processes) will run
501 93 John Freeman
* *PMT port* : pmt.rb's port
502 101 John Freeman
503 1 John Freeman
* *pause before initialization* : the time in seconds between when the artdaq processes have been created and when they're initialized via FHiCL documents; empirically a pause of 5 seconds seems to be sufficient (less than this an errors can occur; see below in the "Troubleshooting" section for more
504 101 John Freeman
505 101 John Freeman
* *log directory* : the directory relative to which lbne-artdaq's pmt/*.log output (a record of what it sent to stdout) will be placed, as well as the individual artdaq process logs, found in boardreader/, eventbuilder/, and aggregator/
506 49 Erik Blaufuss
507 130 John Freeman
* *record directory* : the directory to which metadata about the run (FHiCL documents used, DAQInterface configuration file used, etc.) gets sent
508 49 Erik Blaufuss
509 57 John Freeman
After these individual parameters, one defines the EventBuilderMain and AggregatorMain artdaq processes. Specifically, a process is defined in two lines, where each line should contain "EventBuilder" or "Aggregator", and then define the host and port on which the EventBuilderMain or AggregatorMain will run (to run an artdaq process on the same host as you're on, use "localhost"). Please note that the order of processes matters, and that they should be listed front-end to back-end, i.e., EventBuilders should appear before Aggregators.
510 57 John Freeman
511 187 John Freeman
512 132 John Freeman
h1. Editing or adding RunControl configurations
513 68 John Freeman
514 68 John Freeman
{{collapse(Expand for info here…)
515 91 John Freeman
516 57 John Freeman
Adding a new configuration selectable from RunControl involves two steps: creating a directory with the desired name of the configuration which contains the desired FHiCL documents, and then committing that directory to the git repository. 
517 57 John Freeman
518 57 John Freeman
As of 11/20/14, the FHiCL documents associated with a given configuration are edited within the directory
519 57 John Freeman
520 57 John Freeman
521 57 John Freeman
522 59 John Freeman
where "named_configuration" would be the name of the configuration, in this example. Within this directory, the following files are expected:
523 59 John Freeman
* Aggregator1.fcl and Aggregator2.fcl, used to initialize the two AggregatorMain processes in the DAQ system
524 59 John Freeman
* <named_component>_hw_cfg.fcl, used to initialize the BoardReaderMain process running the fragment generator associated with detector component "named_component". Note that there can be any number of such files associated with a configuration, as long as a given component is registered to RunControl (see below, "Adding new DAQ Components to RunControl")
525 167 John Freeman
526 59 John Freeman
There are existing examples of configurations currently within /data/lbnedaq/config which can be studied (and even copied) for further guidance; a good starting point is the "demo" configuration due to its relative simplicity. Note that the FHiCL documents in these directories contain some variables which are set to "PLACEHOLDER", e.g.
527 68 John Freeman
528 1 John Freeman
 event_builder_count: PLACEHOLDER
529 68 John Freeman
530 68 John Freeman
Note that this is not legal FHiCL, but that DAQInterface will substitute in the appropriate value before using the FHiCL document to initialize an artdaq process; here, for example, it would replace "PLACEHOLDER" with the actual number of EventBuilderMain processes being run.
531 68 John Freeman
532 68 John Freeman
Once you've added a new configuration to /data/lbnedaq/config, you'll need to perform a git commit. Essentially,  /data/lbnedaq/config is not merely a collection of directories naming configurations, but also a git repository. In fact, if you run
533 68 John Freeman
534 68 John Freeman
git log
535 68 John Freeman
536 68 John Freeman
you'll see a history of the commits made to the repository. In order to commit the directory, a couple of steps need to be taken:
537 68 John Freeman
* From /data/lbnedaq/config/, run <pre>git add <named_configuration></pre>. This will "stage" the directory to be committed. Running <pre>git status</pre> should show you something like the following:
538 68 John Freeman
539 68 John Freeman
# On branch master
540 68 John Freeman
# Changes to be committed:
541 68 John Freeman
#   (use "git reset HEAD <file>..." to unstage)
542 68 John Freeman
543 68 John Freeman
#	new file:   helloworld/Aggregator1.fcl
544 68 John Freeman
#	new file:   helloworld/Aggregator2.fcl
545 68 John Freeman
#	new file:   helloworld/component01_hw_cfg.fcl
546 68 John Freeman
#	new file:   helloworld/component02_hw_cfg.fcl
547 68 John Freeman
548 1 John Freeman
549 68 John Freeman
* Next, run <pre>git commit -m "<commit message>"</pre>. The commit message should be your three initials followed by a colon, the name of the configuration followed by a colon, and then a brief description of the new configuration, including its name, e.g.:
550 68 John Freeman
551 68 John Freeman
git commit -m "JCF: helloworld: This configuration does not exist in the actual repo, it's simply used for documentation purposes"
552 68 John Freeman
553 68 John Freeman
Be aware of rules governing strings delimited by double quotes in bash -- i.e., don't try double quoting a word or phrase inside of your commit description. 
554 68 John Freeman
555 68 John Freeman
Now, make sure that the commit took place correctly by running
556 68 John Freeman
557 1 John Freeman
git diff HEAD
558 68 John Freeman
559 68 John Freeman
If your commit is at the head of the master branch, you should see no output; additionally, if you run
560 69 John Freeman
561 57 John Freeman
git log
562 79 John Freeman
563 79 John Freeman
you should be able to see your commit at the top.
564 79 John Freeman
565 79 John Freeman
* Finally, make sure to push your change to the central repository; to do this, simply execute
566 79 John Freeman
567 79 John Freeman
git push origin
568 79 John Freeman
569 79 John Freeman
570 79 John Freeman
and now, if you run 
571 79 John Freeman
572 1 John Freeman
573 132 John Freeman
git diff origin/master
574 132 John Freeman
575 79 John Freeman
576 56 Erik Blaufuss
you should again see no output. Pushing to the central repository is important as this is essentially the backup area for configurations; if a user accidentally overwrites something in /data/lbnedaq/config, as long as commits have been pushed to the central repository there will still be a saved record of configurations before the overwrites took place. In fact, as of this writing (12/3/14), if either (A) edits have been made to the /data/lbnedaq/config directory since its most recent commit, or (B) that commit hasn't been pushed to the central repository, DAQInterface will refuse to execute the initialize transition.
577 49 Erik Blaufuss
578 133 John Freeman
579 49 Erik Blaufuss
h1. Adding new DAQ Components to RunControl
580 49 Erik Blaufuss
581 49 Erik Blaufuss
{{collapse(Expand for info here…)
582 18 John Freeman
The list of available DAQComponents (maps to BoardReader processes) is maintained by RunControl in the file:
583 55 Erik Blaufuss
584 55 Erik Blaufuss
585 49 Erik Blaufuss
586 49 Erik Blaufuss
Each entry (name: host port) defines:
587 18 John Freeman
* name - name of the component, maps to a <name>_hw_cfg.fcl in CfgMgr's configuration directory
588 49 Erik Blaufuss
* host - hostname where BoardReader process will be started
589 49 Erik Blaufuss
* port - XMLRPC port to be used, must be unique and used by other processes.
590 49 Erik Blaufuss
591 49 Erik Blaufuss
For example:
592 49 Erik Blaufuss
593 49 Erik Blaufuss
component01: lbnedaq2 5205
594 133 John Freeman
component02: lbnedaq2 5206
595 133 John Freeman
596 133 John Freeman
Has two components (component01 and component02) both running on lbnedaq2 on ports 5205 and 5206.
597 27 John Freeman
598 49 Erik Blaufuss
*Note* that you will need to kill and re-launch RunControl if you add a component
599 28 John Freeman
600 49 Erik Blaufuss
601 27 John Freeman
h1.  Troubleshooting and FAQ
602 49 Erik Blaufuss
603 1 John Freeman
h2.  Common RunControl issues
604 49 Erik Blaufuss
605 49 Erik Blaufuss
h3. How can I get a list of all RunControl commands?
606 49 Erik Blaufuss
607 50 Erik Blaufuss
608 50 Erik Blaufuss
lbnecmd help
609 1 John Freeman
610 45 John Freeman
will list all available commands for RunControl with some details for help.  
611 49 Erik Blaufuss
612 45 John Freeman
h3.  No real configurations are listed by RunControl
613 49 Erik Blaufuss
614 49 Erik Blaufuss
If you run "lbnecmd listconfigs" and see something like:
615 49 Erik Blaufuss
616 45 John Freeman
Available configs (Name : description)
617 49 Erik Blaufuss
618 1 John Freeman
dummy : Dummy description
619 168 John Freeman
620 147 John Freeman
Instead of your expected configurations, RunControl is not able to connect to CfgMgr.  Please make sure it's running; how to do this, described earlier in the wiki, is simply to execute "lbnecmd check", and launching the configuration manager, also described earlier, can be done via " -c"
621 169 John Freeman
622 170 John Freeman
h3. "lbnecmd check" returns "@Unknown exception '<ProtocolError for localhost:50008/RPC2: -1 >'@"
623 171 John Freeman
624 169 John Freeman
This sometimes happens when the TDU XML-RPC server has died. You can confirm this has happened by running "";  to relaunch it, run " -t".
625 147 John Freeman
626 148 John Freeman
h2.  Common DAQInterface issues
627 148 John Freeman
628 185 John Freeman
As a preliminary: if something goes wrong when running the DAQ, there are two valuable sources of information:
629 146 John Freeman
# The pmt logfile(s), containing the output of the artdaq processes (including the output of the art modules run within them -- so, for example, an exception throw from within a module would appear here). Where to find these logfiles is described in the section "Examining your output", earlier in this wiki. 
630 146 John Freeman
# The RunControl logfile, /home/lbnedaq/.lbnerc.log . This contains both the information sent from DAQInterface to RunControl, as well as diagnostic logging (such as the traceback of exception throws within DAQInterface)
631 173 John Freeman
632 173 John Freeman
In general, when something goes wrong during the running of the DAQ -- e.g., an artdaq process dies, or a sync pulse is attempted when the TDU XML-RPC server isn't alive -- DAQInterface will impose upon itself the "recovery" transition, where it returns itself to the "stopped" state regardless of whatever state it may have currently been in. When this occurs, you'll see something like the following:
633 173 John Freeman
634 173 John Freeman
DAQInterface: "Recover" transition underway
635 173 John Freeman
JCF, 6/12/14 -- for now at least, "Recover" simply kills the artdaq processes
636 173 John Freeman
637 173 John Freeman
Recover transition complete; if running DAQInterface in the background, can press <enter> to return to shell prompt
638 173 John Freeman
639 175 John Freeman
640 173 John Freeman
If a recovery transition occurs, often you can begin using the DAQ again (starting with "lbnecmd init daq") without any issues. However, some issues may be persistent, or require manual intervention. A subset of those issues are described below. If any new ones come up, please contact John Freeman at 
641 184 John Freeman
642 184 John Freeman
h3. *On the initialize transition ("lbnecmd init daq") you see "Unclean working configuration directory /data/lbnedaq/config/ found"*
643 184 John Freeman
644 184 John Freeman
This means that /data/lbnedaq/config has been worked on without commits being made. If you're not using the generic DAQInterface configuration file "config.txt", but rather, have your own copy, you can set "disable configuration check: true" to sidestep this error. This is NOT recommended during standard physics running, but is OK if you're in commissioning. Or, you can either commit the changes (if they were yours) or contact John Freeman,, describing the situation. 
645 184 John Freeman
646 146 John Freeman
h3. *On the initialize transition, you see "<code>pmt.rb -p <port number> was already running on <hostname></code>"*
647 164 John Freeman
648 146 John Freeman
An instance of artdaq's Process Management Tool program, tasked with creating the artdaq processes, is already running on the host and port you've requested for it in the DAQInterface configuration file passed to the DAQInterface application. This can happen if, for example, the DAQInterface program from a previous session was killed off before the usual "lbnecmd terminate daq" transition was issued, a transition which prompts DAQInterface to kill off the pmt.rb process it has control over. Generally, DAQInterface will clean this up and free the port in the process of returning itself to the "stopped" state, but in case it doesn't, there's a script called "" which can be used in the following manner:
649 146 John Freeman
650 149 John Freeman <pmt host> <pmt port>
651 146 John Freeman
652 146 John Freeman
653 146 John Freeman
This script will both kill off the pmt.rb which is clogging the port, as well as the artdaq processes over which it has control.
654 180 John Freeman
655 1 John Freeman
h3. *On the initialize transition ("lbnecmd init daq"), you see "error: [Errno 111] Connection refused"*
656 1 John Freeman
657 180 John Freeman
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 "pause before initialization" variable in the DAQInterface configuration file. Empirically, it appears there needs to be a pause of at least 5 seconds 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.
658 180 John Freeman
659 180 John Freeman
h3. *On the start transition ("lbnecmd start daq"), you see "@TDU RESULT: socket.error caught: [Errno 111] Connection refused    Is the XMLRPC server up?@"*
660 180 John Freeman
661 146 John Freeman
This error will trigger the Recover transition and return you to the stopped state. What it means is that there was an issue connecting to the TDU XML-RPC server (most likely, it wasn't running). Run "lbnecmd check" to see whether it's available; if not, launch it in the usual fashion (i.e., " -t"), and then proceed with the standard DAQ transition sequence ("lbnecmd init daq", etc.)
662 146 John Freeman
663 146 John Freeman
h3. *Regardless of how high the debug level is set to, you don't see any output to screen when you issue transitions to DAQInterface*
664 182 John Freeman
665 1 John Freeman
Chances are that DAQInterface was started in another terminal, and consequently, it's in that terminal where output will appear. If DAQInterface was started via the "" script, then as of May-5-2015, all output is directed to /data/lbnedaq/daqlogs/daqinterface/DI.log, so running "tail -f  /data/lbnedaq/daqlogs/daqinterface/DI.log" from another terminal will guarantee you can see DAQInterface output in real time. Please note this file is appended to, not overwritten, so only the end of the file will be of interest. 
666 1 John Freeman
667 1 John Freeman
{{collapse(Of developer interest)
668 1 John Freeman
h3.  *Error handling*
669 1 John Freeman
670 1 John Freeman
As of this writing (11/14/14) certain potential problems have been anticipated and are handled within DAQInterface. These problems include:
671 1 John Freeman
# An artdaq process returns an error state after a transition request, or an exception is thrown by the XML-RPC library during the request
672 51 John Freeman
# During periodic checks, one or more artdaq processes expected to exist are not found
673 84 John Freeman
674 77 John Freeman
In either case, an error is reported via 0MQ to RunControl, 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). 
675 77 John Freeman
676 1 John Freeman
h3. *Your change to the DAQInterface configuration file or the code doesn't seem to do anything*
677 146 John Freeman
678 1 John Freeman
Make sure you kill the existing daqinterface process and restart it
679 1 John Freeman
680 183 John Freeman
681 183 John Freeman
682 183 John Freeman
h2. Common lbne-artdaq issues
683 183 John Freeman
684 183 John Freeman
h3. The message "Failed to connect to shared memory segment" appears in the logfile
685 183 John Freeman
686 183 John Freeman
The full message is "<code>Failed to connect to shared memory segment, errno = 22.  Please check if a stale shared memory segment needs to be cleaned up. (ipcs, ipcrm -m <segId>)</code>". Go to the system on which the process that issued the message is running (e.g., if it was an AggregatorMain process on lbnedaq2, go there) and run <code>ipcs</code>. You should see something like the following:
687 183 John Freeman
688 183 John Freeman
------ Shared Memory Segments --------
689 183 John Freeman
key        shmid      owner      perms      bytes      nattch     status      
690 183 John Freeman
0x40471518 4161536    lbnedaq    666        16777216   0          
691 183 John Freeman
692 1 John Freeman
This is the offending memory segment. To remove it, run the following (where here, we'll assume it's the one with shared memory ID 4161536, above-- of course you'll most likely see a different ID): <code>ipcrm -m  4161536</code>. Now, if you run <code>ipcs</code> again, the segment should not be listed; furthermore, the error should not appear again if you run again with the DAQ.