Running DAQ Interface » History » Version 122

John Freeman, 03/25/2015 12:00 PM

1 122 John Freeman
* UNDER REVISION AS OF 12:00 PM CDT, March 25 *
2 122 John Freeman
3 122 John Freeman
4 58 John Freeman
5 58 John Freeman
6 96 John Freeman
7 96 John Freeman
8 49 Erik Blaufuss
h1. Getting help
9 1 John Freeman
10 78 John Freeman
If, after reading this document (in particular, the "Troubleshooting and FAQ" section) you run into issues, or have questions, please contact:
11 49 Erik Blaufuss
* DAQInterface
12 49 Erik Blaufuss
** John Freeman -
13 62 John Freeman
* RunControl
14 49 Erik Blaufuss
** Erik Blaufuss -
15 66 John Freeman
* Configuration Manager
16 66 John Freeman
** Jon Paley -
17 1 John Freeman
18 102 Erik Blaufuss
h1. Logbook
19 102 Erik Blaufuss
20 102 Erik Blaufuss
Please document all changes, software updates, and operational activities to the ELog:
21 102 Erik Blaufuss
22 102 Erik Blaufuss
23 95 John Freeman
24 120 John Freeman
h1. Brief preliminaries
25 120 John Freeman
26 121 John Freeman
This guide assumes you have access to 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, etc.). Finally, when you see a <pre>…</pre> in example output, that is to be interpreted as a placeholder for output which is considered irrelevant to the point being explained.
27 120 John Freeman
28 1 John Freeman
h1. Starting DAQInterface and Run Control
29 1 John Freeman
30 66 John Freeman
The DAQ software, consisting of RunControl, the configuration manager and DAQInterface (as well as the artdaq processes it controls) is designed to be run on, using the lbnedaq account. If you need access to the account, please contact one of us.
31 49 Erik Blaufuss
32 91 John Freeman
The installed code is located at To get started, login and first setup the environment:
33 49 Erik Blaufuss
34 30 John Freeman
35 33 John Freeman
36 91 John Freeman
cd /data/lbnedaq/daqarea
37 1 John Freeman
source fireup
38 1 John Freeman
39 1 John Freeman
40 91 John Freeman
This will take you into the /data/lbnedaq/daqarea/lbnerc directory. It's a good idea to check whether lbnecontrol (the RunControl application), DAQInterface (the component which intermediates between RunControl, the configuration manager, and the artdaq processes) and the configuration manager are already running; if they are, the instructions below won't work. Also worth noting is that as of 11/21/14, attempts to use multiple DAQs (implying multiple instances of RunControl, DAQInterface, etc.) has not been attempted and likely will not work. To check for RunControl and DAQInterface, you can try:
41 1 John Freeman
42 1 John Freeman
43 49 Erik Blaufuss
lbnecmd check
44 1 John Freeman
45 1 John Freeman
46 61 John Freeman
This will display the current state of DAQInterface and RunControl. The example below shows that both RunControl and DAQInterface are running, but the DAQ run is in the stopped state:
47 49 Erik Blaufuss
48 49 Erik Blaufuss
(env)[lbnedaq@lbne35t-gateway01 lbnerc]$ lbnecmd check
49 49 Erik Blaufuss
lbnecontrol: running
50 49 Erik Blaufuss
daqint@localhost:5770 (synchronous): stopped
51 49 Erik Blaufuss
52 1 John Freeman
53 73 John Freeman
If RunControl is running, and at some point DAQInterface was running but has since been killed:
54 73 John Freeman
55 73 John Freeman
lbnecontrol: running
56 73 John Freeman
daqint@localhost:5770 (synchronous): missing
57 73 John Freeman
58 91 John Freeman
(In this case, just restart DAQInterface -- how to do this is described shortly).
59 73 John Freeman
60 49 Erik Blaufuss
If RunControl is not running, you'll see something like:
61 1 John Freeman
62 49 Erik Blaufuss
(env)[lbnedaq@lbne35t-gateway01 lbnerc]$ lbnecmd check
63 49 Erik Blaufuss
check failed: '[Errno 111] Connection refused'.  Is lbnecontrol running?
64 1 John Freeman
65 1 John Freeman
66 61 John Freeman
To check whether the configuration manager is running, you can simply use Linux commands:
67 61 John Freeman
68 61 John Freeman
69 61 John Freeman
ps aux | grep -v grep | grep CfgMgrApp
70 61 John Freeman
71 61 John Freeman
72 109 Thomas Dealtry
This will either return info on CfgMgrApp (the actual name of the configuration manager process), or print nothing if it's not running. Similarly, you can check whether the TDU XMLRPC server is running using:
73 71 John Freeman
74 71 John Freeman
75 109 Thomas Dealtry
ps aux | grep -v grep | grep tdu
76 1 John Freeman
77 1 John Freeman
78 109 Thomas Dealtry
In fact, it's possible to use Linux commands to check the status of all four programs:
79 109 Thomas Dealtry
80 109 Thomas Dealtry
81 109 Thomas Dealtry
ps aux | grep -v grep | egrep -e lbnecontrol -e daqinterface -e CfgMgrApp -e tdu
82 109 Thomas Dealtry
83 109 Thomas Dealtry
84 110 John Freeman
If you wish to kill any of these processes (described in the next section), the PID (process ID) to use is supplied as the second field in each row returned by the "ps aux" command.
85 105 John Freeman
86 109 Thomas Dealtry
h3. Cleanup: killing RunControl, DAQInterface, the configuration manager, and the TDU XMLRPC server
87 105 John Freeman
88 105 John Freeman
To begin using the DAQ, you'll want to kill off any existing RunControl and/or DAQInterface processes. With the process IDs obtained from the command described in the previous section, you can kill any pre-existing such processes. Keep in mind, of course, that if these processes are running, it might mean that someone else is using the DAQ, or that someone else who's done using it forgot to clean up. 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. To kill them, again keeping in mind that the second field returned from "ps aux" is the process id (PID), use:
89 105 John Freeman
90 105 John Freeman
kill <PID>
91 105 John Freeman
92 110 John Freeman
If DAQInterface was in any state other than "stopped" at the time it was killed, it's quite possible that it's left "orphaned" artdaq processes. If this is the case, you'll want to clean these up before trying to run the DAQ again, as they'll block the ports if they remain alive as "zombie" processes. Check the DAQInterface configuration file (defaults to lbnerc/docs/config.txt unless an alternate was supplied via the "-f" option to DAQInterface) to see which node the PMT (Process Management Tool) was running on, and check for it with
93 105 John Freeman
94 105 John Freeman
ps aux | grep -v grep | grep pmt.rb
95 105 John Freeman
96 105 John Freeman
Use this to get the process ID to kill it. Of course, also be aware that if artdaq processes were in communication with hardware when the orphaning occurred, killing them off might result in issues for the hardware, but the specifics of any hardware issues that may arise go beyond the scope of this document.
97 105 John Freeman
98 1 John Freeman
h3. Starting RunControl
99 49 Erik Blaufuss
100 49 Erik Blaufuss
To start RunControl (after loading environment as above):
101 60 John Freeman
102 104 John Freeman
rm -f /tmp/  # (This should only be necessary if RunControl software wasn't stopped cleanly)
103 49 Erik Blaufuss
lbnecmd launch
104 49 Erik Blaufuss
105 1 John Freeman
106 1 John Freeman
h3. Starting DAQInterface
107 1 John Freeman
108 61 John Freeman
To start DAQInterface (after loading environment as above), the basic command is:
109 1 John Freeman
110 82 John Freeman
daqinterface -n daqint -r 5570 -c localhost -H localhost -f <daqinterface file> &
111 1 John Freeman
112 82 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. 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 "Configuring DAQInterface" for more. 
113 82 John Freeman
114 82 John Freeman
If multiple users with different terminals wish to check the DAQ output, it is recommended to try:
115 1 John Freeman
116 82 John Freeman
stdbuf -oL daqinterface -n daqint -r 5570 -c localhost -H localhost -f <daqinterface file> >>~/DI.log 2>&1 &
117 1 John Freeman
118 91 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)
119 82 John Freeman
120 1 John Freeman
h3. Starting the configuration manager
121 1 John Freeman
122 1 John Freeman
Please see the "Starting up the CfgMgrApp on lbne35t-gateway01" section of Jon Paley's documentation here:
123 109 Thomas Dealtry
124 109 Thomas Dealtry
h3. Starting the TDU XMLRPC server
125 109 Thomas Dealtry
126 109 Thomas Dealtry
127 109 Thomas Dealtry
tdu -T -P 10001 -H localhost -r 50008
128 109 Thomas Dealtry
129 109 Thomas Dealtry
130 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.
131 109 Thomas Dealtry
132 109 Thomas Dealtry
See [[Starting and using TDUControl]] for more details.
133 62 John Freeman
134 61 John Freeman
h1. Configuring and starting Runs
135 1 John Freeman
136 107 John Freeman
Now, you can take the DAQ system through the standard transitions to start a DAQ run.  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. DAQInterface will also report when transitions are complete -- e.g., at the end of the "initialize" transition, you'd see:
137 49 Erik Blaufuss
138 49 Erik Blaufuss
Initialize transition complete; if running DAQInterface in the background, can press <enter> to return to shell prompt
139 1 John Freeman
140 108 John Freeman
Note that if a high "debug level" has been set (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. Described in more detail later, the chain of states (in quotes) and transitions (in italics) in the DAQ system can be represented as follows:
141 1 John Freeman
142 108 John Freeman
143 108 John Freeman
144 117 John Freeman
"stopped" -> _init_ -> "ready" -> _start_ -> "running" -> _pause_ -> "ready" -> _resume_ -> "running" -> _stop_ -> "ready" -> _terminate_ -> "stopped"
145 108 John Freeman
146 108 John Freeman
147 1 John Freeman
148 94 John Freeman
h2.  Selecting a run configuration and DAQ components
149 49 Erik Blaufuss
150 1 John Freeman
*Before initializing or starting a DAQ run*, a configuration and set of DAQComponents must be selected.  This is done via RunControl.
151 1 John Freeman
152 49 Erik Blaufuss
h3. List and select a configuration:
153 1 John Freeman
154 62 John Freeman
To see the list of available configurations (queried from the configuration manager):
155 49 Erik Blaufuss
156 49 Erik Blaufuss
lbnecmd listconfigs
157 1 John Freeman
158 49 Erik Blaufuss
Will return a list of configs:
159 49 Erik Blaufuss
160 49 Erik Blaufuss
Available configs (Name : description)
161 1 John Freeman
162 111 John Freeman
8xssp_with_nova_sync : Sorry, no description found.
163 111 John Freeman
6xssp_ext : Sorry, no description found.
164 111 John Freeman
2xssp_ssp01_led_ssp02_tstamp : Sorry, no description found.
165 111 John Freeman
demo : This is a demo.  Testing 1, 2, 3…
166 30 John Freeman
167 1 John Freeman
168 49 Erik Blaufuss
Current selected config: No Config
169 49 Erik Blaufuss
170 111 John Freeman
This lists all available configs, as well as the current selected config (Note, default config is "No Config").  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:
171 49 Erik Blaufuss
172 49 Erik Blaufuss
lbnecmd setconfig demo
173 1 John Freeman
174 90 John Freeman
This will return "OK" if successful; "lbnecmd listconfigs" will then show this as the current config.  If the specified configuration is not known, an error is returned. Instructions on how to add a configuration are given later in this document.
175 1 John Freeman
176 49 Erik Blaufuss
h3. List and select DAQ components.
177 1 John Freeman
178 62 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
179 90 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.
180 38 John Freeman
181 1 John Freeman
To see the list of available DAQ components:
182 49 Erik Blaufuss
183 1 John Freeman
lbnecmd listdaqcomps
184 49 Erik Blaufuss
185 62 John Freeman
Will return a list of components available and selected (*Default* is ALL available components), e.g.:
186 1 John Freeman
187 112 John Freeman
188 112 John Freeman
component01 (lbnedaq2:5205)
189 112 John Freeman
component02 (lbnedaq2:5206)
190 112 John Freeman
191 112 John Freeman
ssp08 (lbnedaq1:5214)
192 112 John Freeman
193 112 John Freeman
194 112 John Freeman
component01 (lbnedaq2:5205)
195 112 John Freeman
component02 (lbnedaq2:5206)
196 112 John Freeman
197 112 John Freeman
ssp08 (lbnedaq1:5214)
198 62 John Freeman
199 113 John Freeman
The components are shown by name, along with the requested host/port to run the BoardReaderMain process on. You can then select a list of DAQ components to use in the run:
200 1 John Freeman
201 118 John Freeman
lbnecmd setdaqcomps component0{1,2}
202 49 Erik Blaufuss
203 118 John Freeman
(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 compnents are not known, an error is returned.
204 49 Erik Blaufuss
To change the list of available components, see below.
205 29 John Freeman
206 91 John Freeman
h2. Initializing, starting, stopping and terminating a Run
207 1 John Freeman
208 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:
209 1 John Freeman
210 49 Erik Blaufuss
lbnecmd check
211 1 John Freeman
212 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.
213 1 John Freeman
214 92 John Freeman
First, take DAQInterface from the "stopped" to the "ready" state; this will create the artdaq processes on the hosts you selected (DAQ components), and initialize them with the FHiCL documents:
215 1 John Freeman
216 1 John Freeman
lbnecmd init daq
217 1 John Freeman
218 1 John Freeman
219 49 Erik Blaufuss
Take DAQInterface from the "ready" to the "running" state, in order to begin taking data:
220 29 John Freeman
221 1 John Freeman
lbnecmd start daq
222 29 John Freeman
223 49 Erik Blaufuss
Note: the current run number is displayed when DAQ is in the running state using the "lbnecmd check" command:
224 49 Erik Blaufuss
225 49 Erik Blaufuss
lbnecmd check
226 49 Erik Blaufuss
lbnecontrol: running
227 49 Erik Blaufuss
Run number: 207
228 49 Erik Blaufuss
Run configuration: demo
229 1 John Freeman
230 49 Erik Blaufuss
daqint@localhost:5570 (synchronous): running
231 49 Erik Blaufuss
232 49 Erik Blaufuss
233 49 Erik Blaufuss
Pause the running of the DAQ, putting DAQInterface into the "paused" state.  This will cause the current open output file to be closed and given a name reflecting the current run number:
234 22 John Freeman
235 21 John Freeman
lbnecmd pause daq
236 42 John Freeman
237 41 John Freeman
238 1 John Freeman
Resume the running of the DAQ, putting returning to the "running" state.  This will restart data taking to a new output file:
239 48 John Freeman
240 48 John Freeman
lbnecmd resume daq
241 48 John Freeman
242 48 John Freeman
243 48 John Freeman
Halt the running of the DAQ, returning DAQInterface to the "ready" state from the "running" state:
244 48 John Freeman
245 48 John Freeman
lbnecmd stop daq
246 49 Erik Blaufuss
247 49 Erik Blaufuss
From the ready state, you can start a new run with the same configuration and DAQ components you originally selected. 
248 62 John Freeman
*NOTE* To select a new configuration or DAQ component set, you must kill all ArtDAQ processes and return DAQInterface to its "stopped" state with the "terminate" command:
249 1 John Freeman
250 1 John Freeman
251 1 John Freeman
lbnecmd terminate daq
252 1 John Freeman
253 67 Erik Blaufuss
254 67 Erik Blaufuss
If you want to stop all RunControl processes (known as "lbnecontrol"):
255 67 Erik Blaufuss
256 67 Erik Blaufuss
lbnecmd kill
257 67 Erik Blaufuss
258 67 Erik Blaufuss
After this, you will need to relaunch RunControl as above.
259 1 John Freeman
260 49 Erik Blaufuss
h2. After your DAQ run.
261 1 John Freeman
262 49 Erik Blaufuss
Once you've completed your run, there are a few things you can look at. 
263 48 John Freeman
264 76 John Freeman
h3. The DAQ log
265 76 John Freeman
266 114 John Freeman
A record of the DAQ's output will be saved in the subdirectory pmt/ relative to where you specified the output logfiles; thus given the "log directory" setting in the example DAQInterface configuration file below, you'd find the output in /data/lbnedaq/daqlogs/pmt/.
267 76 John Freeman
268 76 John Freeman
h3. The run record
269 76 John Freeman
270 91 John Freeman
Also, a record of the FHiCL documents sent to the artdaq processes, the configuration file used to control DAQInterface, and some further information will have been saved; as of this writing (12/3/14) the directory in which this can be found defaults to /data/lbnedaq/run_records/<run number>. 
271 92 John Freeman
** PLEASE NOTE that there may be slight differences between the saved FHiCL documents and the FHiCL documents specified in the DAQInterface configuration file (those that control the EventBuilderMain processes) and the run configuration (those that control the BoardReaderMain and AggregatorMain processes). The saved FHiCL document name is standardized to <processtype>_<host>_<port>_r<run number>.fcl, so, e.g, "EventBuilder_lbnedaq2_5235_r286.fcl" would be the saved name of /data/lbnedaq/fcl/EventBuilder_demo1.fcl, listed in the example DAQInterface configuration file above, assuming datataking was performed in run 286. 
272 1 John Freeman
** More importantly, the FHiCL document actually sent to the artdaq process may be slightly different than the FHiCL document provided for DAQInterface; 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). It is this post-bookkeeping FHiCL document which actually gets sent to the processes which gets saved to the output directory. 
273 115 John Freeman
** The "further information" mentioned above is stored in a file of the form "metadata_r<run number>.txt"; it includes the configuration chosen for the run, the components used, as well as the commit hashes for the lbne-artdaq, lbnerc, and configuration directory used. Also provided are the process management tool (PMT) and individual artdaq process logs; please note that as of this writing (3/19/15), while the algorithm used to determine these logs hasn't yet been incorrect, there are in-principle edge cases in which the wrong log could be provided, so be aware -- and in particular, check the line "Started run <runnumber>" in the PMT logfile for confirmation that you have what you want. 
274 115 John Freeman
275 119 John Freeman
As an example, in /data/lbnedaq/run_records/778 (the directory for run 778), the metadata file looks like the following:
276 72 John Freeman
277 72 John Freeman
Config name: demo
278 72 John Freeman
Component #0: component01
279 1 John Freeman
Component #1: component02
280 119 John Freeman
lbne-artdaq commit: 0f0f9be1c63a3b487170579c887ce79944eca6f8
281 119 John Freeman
lbnerc commit: 92935f2702c5e0aa732fd3cc9ff6758e1a0c288c
282 119 John Freeman
/data/lbnedaq/config/ commit: 97d8b222742a41d5d10ea942a063ddfacac3ce93
283 114 John Freeman
284 114 John Freeman
285 119 John Freeman
pmt logfile(s): lbnedaq3:/data/lbnedaq/daqlogs/pmt/pmt-25771*.log
286 114 John Freeman
287 1 John Freeman
boardreader logfiles: 
288 119 John Freeman
289 119 John Freeman
290 114 John Freeman
291 114 John Freeman
eventbuilder logfiles: 
292 119 John Freeman
293 119 John Freeman
294 119 John Freeman
295 114 John Freeman
296 114 John Freeman
aggregator logfiles: 
297 119 John Freeman
298 119 John Freeman
299 119 John Freeman
300 1 John Freeman
301 76 John Freeman
302 81 John Freeman
h3. Output of the Art modules
303 76 John Freeman
304 81 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. The other AggregatorMain typically will run other RootOutput 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.
305 76 John Freeman
306 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:
307 76 John Freeman
308 76 John Freeman
309 76 John Freeman
cd <lbne-artdaq basedir>
310 76 John Freeman
source setupLBNEARTDAQ
311 76 John Freeman
rawEventDump -s <rootfile> -n <max events>
312 76 John Freeman
313 76 John Freeman
314 76 John Freeman
where here, <lbne-artdaq basedir> is the parent directory of the lbne-artdaq package, <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. The output of this command will look something like the following:
315 76 John Freeman
316 76 John Freeman
317 81 John Freeman
%MSG-i MF_INIT_OK:  art 01-Dec-2014 16:13:59 CST JobSetup 
318 76 John Freeman
Messagelogger initialization complete.
319 76 John Freeman
320 81 John Freeman
%MSG-i PathConfiguration:  art 01-Dec-2014 16:14:00 CST JobSetup 
321 76 John Freeman
Multiple end paths have been combined into one end path,
322 76 John Freeman
"end_path" since order is irrelevant.
323 76 John Freeman
324 76 John Freeman
325 81 John Freeman
01-Dec-2014 16:14:00 CST  Initiating request to open file /tmp/lbne35t_r000270_sr01_20141201T221127.root
326 81 John Freeman
01-Dec-2014 16:14:00 CST  Successfully opened file /tmp/lbne35t_r000270_sr01_20141201T221127.root
327 1 John Freeman
328 76 John Freeman
Package             |Version             |Timestamp           
329 81 John Freeman
artdaq-core         |v1_04_06            |01-Dec-2014 21:59:51 UTC
330 81 John Freeman
artdaq              |v1_12_04            |01-Dec-2014 22:01:57 UTC
331 81 John Freeman
lbne-artdaq         |v0_00_08            |01-Dec-2014 22:00:18 UTC
332 81 John Freeman
lbne-artdaq         |v0_07_00            |01-Dec-2014 22:02:57 UTC
333 76 John Freeman
334 81 John Freeman
Begin processing the 1st record. run: 270 subRun: 1 event: 1 at 01-Dec-2014 16:14:00 CST
335 76 John Freeman
336 81 John Freeman
DAQ......... | daq........... | TOY1................. | std::vector<artdaq::Fragment> | artdaq::Fragments.... | ...2
337 1 John Freeman
DAQAG....... | TriggerResults | ..................... | art::TriggerResults.......... | art::TriggerResults.. | ...-
338 76 John Freeman
339 81 John Freeman
Total products (present, not present): 8 (2, 6).
340 76 John Freeman
341 1 John Freeman
342 76 John Freeman
DAQAG....... | BuildInfo... | LbneArtdaq........... | std::vector<artdaq::PackageBuildInfo> | artdaq::PackageBuildInfos | ...4
343 76 John Freeman
344 76 John Freeman
Total products (present, not present): 1 (1, 0).
345 76 John Freeman
346 81 John Freeman
01-Dec-2014 16:14:00 CST  Closed file /tmp/lbne35t_r000270_sr01_20141201T221127.root
347 76 John Freeman
348 76 John Freeman
TrigReport ---------- Event  Summary ------------
349 76 John Freeman
TrigReport Events total = 1 passed = 1 failed = 0
350 76 John Freeman
351 76 John Freeman
TrigReport ------ Modules in End-Path: end_path ------------
352 76 John Freeman
TrigReport  Trig Bit#    Visited     Passed     Failed      Error Name
353 76 John Freeman
TrigReport     0    0          1          1          0          0 printBuildInfo
354 76 John Freeman
TrigReport     0    0          1          1          0          0 out1
355 76 John Freeman
356 76 John Freeman
TimeReport ---------- Time  Summary ---[sec]----
357 1 John Freeman
TimeReport CPU = 0.003361 Real = 0.003000
358 1 John Freeman
359 76 John Freeman
Art has completed and will exit with status 0.
360 76 John Freeman
361 76 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 two fragments of type TOY1, produced by the ToySimulator fragment generator. Finally, a listing of passed 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.
362 81 John Freeman
363 84 John Freeman
h1. Configuring DAQInterface: the DAQInterface configuration file
364 91 John Freeman
365 92 John Freeman
DAQInterface has 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  location and ports for artdaq processes, location of lbne-artdaq software, debug (log) level, etc). These can be changed before the DAQInterface process is started. It's expected that for normal operations, these 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, found in docs/config.txt (relative to /data/lbnedaq/daqarea/lbnerc); it should look something like the following:
366 1 John Freeman
367 1 John Freeman
368 100 John Freeman
lbne-artdaq: /data/lbnedaq/daqarea/lbne-artdaq-base/build_lbne-artdaq
369 91 John Freeman
370 1 John Freeman
PMT host: lbnedaq3
371 100 John Freeman
PMT port: 5400
372 1 John Freeman
373 49 Erik Blaufuss
pause before initialization: 5
374 49 Erik Blaufuss
375 49 Erik Blaufuss
# debug level can range from 0 to 3 (increasing order of verbosity)
376 49 Erik Blaufuss
debug level: 1
377 49 Erik Blaufuss
378 49 Erik Blaufuss
log directory:   /data/lbnedaq/daqlogs
379 49 Erik Blaufuss
380 91 John Freeman
record directory: /data/lbnedaq/run_records
381 49 Erik Blaufuss
382 116 John Freeman
# If this file is "config.txt" -- i.e., the standard, non-expert,
383 116 John Freeman
# non-testing version of the DAQInterface configuration file -- do not
384 116 John Freeman
# set "disable configuration check" to "true"
385 116 John Freeman
386 101 John Freeman
disable configuration check: false
387 101 John Freeman
388 101 John Freeman
TDU XMLRPC port: 0
389 91 John Freeman
390 91 John Freeman
EventBuilder host: lbnedaq2
391 48 John Freeman
EventBuilder port: 5235
392 91 John Freeman
393 91 John Freeman
EventBuilder host: lbnedaq2
394 91 John Freeman
EventBuilder port: 5236
395 48 John Freeman
396 91 John Freeman
Aggregator host: lbnedaq2
397 91 John Freeman
Aggregator port: 5265
398 48 John Freeman
399 91 John Freeman
Aggregator host: lbnedaq2
400 1 John Freeman
Aggregator port: 5266
401 1 John Freeman
402 1 John Freeman
403 1 John Freeman
404 92 John Freeman
The meaning of these parameters is as follows:
405 92 John Freeman
406 92 John Freeman
* *lbne-artdaq* : the directory in which the desired build of lbne-artdaq to use is located
407 92 John Freeman
408 1 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
409 100 John Freeman
* *PMT port* : pmt.rb's port
410 92 John Freeman
411 92 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
412 1 John Freeman
413 92 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. 
414 92 John Freeman
415 116 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/
416 93 John Freeman
417 93 John Freeman
* *record directory* : the directory to which metadata about the run (FHiCL documents used, DAQInterface configuration file used, etc.) gets sent
418 101 John Freeman
419 1 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. 
420 101 John Freeman
421 101 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":
422 49 Erik Blaufuss
423 116 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.
424 49 Erik Blaufuss
425 57 John Freeman
h1. Adding new configurations to RunControl
426 57 John Freeman
427 68 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. 
428 68 John Freeman
429 91 John Freeman
As of 11/20/14, the FHiCL documents associated with a given configuration are edited within the directory
430 57 John Freeman
431 57 John Freeman
432 57 John Freeman
433 57 John Freeman
where "named_configuration" would be the name of the configuration, in this example. Within this directory, the following files are expected:
434 57 John Freeman
* Aggregator1.fcl and Aggregator2.fcl, used to initialize the two AggregatorMain processes in the DAQ system
435 57 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")
436 59 John Freeman
437 59 John Freeman
There are existing examples of configurations currently within /data/lbnedaq/config which can be studied (and even copied) for further guidance; however, please disregard the "tmp1" and "tmp2" configurations. Note that the FHiCL documents in these directories contain some variables which are set to "PLACEHOLDER", e.g.
438 59 John Freeman
439 1 John Freeman
 event_builder_count: PLACEHOLDER
440 59 John Freeman
441 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.
442 1 John Freeman
443 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
444 68 John Freeman
445 68 John Freeman
git log
446 68 John Freeman
447 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:
448 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:
449 68 John Freeman
450 68 John Freeman
# On branch master
451 68 John Freeman
# Changes to be committed:
452 68 John Freeman
#   (use "git reset HEAD <file>..." to unstage)
453 68 John Freeman
454 68 John Freeman
#	new file:   helloworld/Aggregator1.fcl
455 68 John Freeman
#	new file:   helloworld/Aggregator2.fcl
456 68 John Freeman
#	new file:   helloworld/component01_hw_cfg.fcl
457 68 John Freeman
#	new file:   helloworld/component02_hw_cfg.fcl
458 68 John Freeman
459 68 John Freeman
460 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.:
461 68 John Freeman
462 1 John Freeman
git commit -m "JCF: helloworld: This configuration does not exist in the actual repo, it's simply used for documentation purposes"
463 68 John Freeman
464 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. 
465 68 John Freeman
466 68 John Freeman
Now, make sure that the commit took place correctly by running
467 68 John Freeman
468 68 John Freeman
git diff HEAD
469 68 John Freeman
470 68 John Freeman
If your commit is at the head of the master branch, you should see no output; additionally, if you run
471 1 John Freeman
472 68 John Freeman
git log
473 68 John Freeman
474 69 John Freeman
you should be able to see your commit at the top.
475 57 John Freeman
476 79 John Freeman
* Finally, make sure to push your change to the central repository; to do this, simply execute
477 79 John Freeman
478 79 John Freeman
git push origin
479 79 John Freeman
480 79 John Freeman
481 79 John Freeman
and now, if you run 
482 79 John Freeman
483 79 John Freeman
484 79 John Freeman
git diff origin/master
485 79 John Freeman
486 79 John Freeman
487 91 John Freeman
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. 
488 79 John Freeman
489 56 Erik Blaufuss
h1. Adding new DAQ Components to RunControl
490 49 Erik Blaufuss
491 49 Erik Blaufuss
The list of available DAQComponents (maps to BoardReader processes) is maintained by RunControl in the file:
492 49 Erik Blaufuss
493 49 Erik Blaufuss
494 18 John Freeman
495 55 Erik Blaufuss
Each entry (name: host port) defines:
496 55 Erik Blaufuss
* name - name of the component, maps to a <name>_hw_cfg.fcl in CfgMgr's configuration directory
497 49 Erik Blaufuss
* host - hostname where BoardReader process will be started
498 49 Erik Blaufuss
* port - XMLRPC port to be used, must be unique and used by other processes.
499 18 John Freeman
500 49 Erik Blaufuss
For example:
501 49 Erik Blaufuss
502 49 Erik Blaufuss
component01: lbnedaq2 5205
503 49 Erik Blaufuss
component02: lbnedaq2 5206
504 49 Erik Blaufuss
505 49 Erik Blaufuss
Has two components (component01 and component02) both running on lbnedaq2 on ports 5205 and 5206.
506 27 John Freeman
507 49 Erik Blaufuss
h1.  Troubleshooting and FAQ
508 28 John Freeman
509 49 Erik Blaufuss
h2.  Common RunControl issues
510 27 John Freeman
511 49 Erik Blaufuss
h3. How can I get a list of all RunControl commands?
512 1 John Freeman
513 49 Erik Blaufuss
514 49 Erik Blaufuss
lbnecmd help
515 49 Erik Blaufuss
516 50 Erik Blaufuss
will list all available commands for RunControl with some details for help.  
517 50 Erik Blaufuss
518 1 John Freeman
h3.  No real configurations are listed by RunControl
519 45 John Freeman
520 49 Erik Blaufuss
If you run "lbnecmd listconfigs" and see something like:
521 45 John Freeman
522 49 Erik Blaufuss
Available configs (Name : description)
523 49 Erik Blaufuss
524 49 Erik Blaufuss
dummy : Dummy description
525 45 John Freeman
526 49 Erik Blaufuss
Instead of your expected configurations, RunControl is not able to connect to CfgMgr.  Please make sure it's running (
527 1 John Freeman
528 49 Erik Blaufuss
h2.  Common DAQInterface issues
529 49 Erik Blaufuss
530 49 Erik Blaufuss
h3.  *Error handling*
531 49 Erik Blaufuss
532 49 Erik Blaufuss
As of this writing (11/14/14) certain potential problems have been anticipated and are handled within DAQInterface. These problems include:
533 49 Erik Blaufuss
# An artdaq process returns an error state after a transition request, or an exception is thrown by the XML-RPC library during the request
534 49 Erik Blaufuss
# During periodic checks, one or more artdaq processes expected to exist are not found
535 49 Erik Blaufuss
536 49 Erik Blaufuss
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). 
537 49 Erik Blaufuss
538 84 John Freeman
h3. *Your change to the DAQInterface configuration file or the code doesn't seem to do anything*
539 49 Erik Blaufuss
540 1 John Freeman
Make sure you kill the existing daqinterface process and restart it
541 49 Erik Blaufuss
542 54 John Freeman
h3. *On the initial transition ("lbnecmd init daq"), you see "error: [Errno 111] Connection refused"*
543 49 Erik Blaufuss
544 91 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.
545 54 John Freeman
546 49 Erik Blaufuss
h3. *On the initial transition, you see a regularly updating printout saying "Waiting for all processes to be launched"*
547 1 John Freeman
548 1 John Freeman
Seeing one or two of these is fine. If, after several seconds, something like the following
549 1 John Freeman
550 1 John Freeman
Waiting for all processes to be launched; if zombie pmt.rb is running on localhost please kill it and this program (PID 31820)
551 1 John Freeman
552 1 John Freeman
keeps getting output to screen, it means there's a problem initializing. In this case, the current (11/12/14) course of action is to externally kill DAQInterface using the PID listed; also, it's possible that there may already be a pmt.rb executable running on the desired host, blocking the launch of a new one due to a port conflict, in which case you should log onto the host (assuming you're not already on it), and run 
553 1 John Freeman
554 1 John Freeman
ps aux | grep -v grep | grep pmt.rb 
555 51 John Freeman
556 84 John Freeman
to see if this is the case. If it's not and you can't think of what might be wrong (is the configuration manager running? have you double-checked the DAQInterface configuration file?), then try increasing the debug level in the DAQInterface configuration file for your next run-through, as this will likely shed light on the nature of the problem.
557 77 John Freeman
558 77 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*
559 1 John Freeman
560 79 John Freeman
Chances are that DAQInterface was started in another terminal, and consequently, it's in that terminal where output will appear. This issue can be circumvented by redirecting DAQInterface output into a file; how this can be accomplished is described elsewhere in this document.