Running DAQ Interface » History » Version 106

John Freeman, 03/10/2015 05:23 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 66 John Freeman
** Jon Paley -
14 1 John Freeman
15 102 Erik Blaufuss
h1. Logbook
16 102 Erik Blaufuss
17 102 Erik Blaufuss
Please document all changes, software updates, and operational activities to the ELog:
18 102 Erik Blaufuss
19 102 Erik Blaufuss
20 95 John Freeman
21 1 John Freeman
h1. Starting DAQInterface and Run Control
22 1 John Freeman
23 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.
24 49 Erik Blaufuss
25 91 John Freeman
The installed code is located at To get started, login and first setup the environment:
26 49 Erik Blaufuss
27 30 John Freeman
28 33 John Freeman
29 91 John Freeman
cd /data/lbnedaq/daqarea
30 1 John Freeman
source fireup
31 1 John Freeman
32 1 John Freeman
33 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:
34 1 John Freeman
35 1 John Freeman
36 49 Erik Blaufuss
lbnecmd check
37 1 John Freeman
38 1 John Freeman
39 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:
40 49 Erik Blaufuss
41 49 Erik Blaufuss
(env)[lbnedaq@lbne35t-gateway01 lbnerc]$ lbnecmd check
42 49 Erik Blaufuss
lbnecontrol: running
43 49 Erik Blaufuss
daqint@localhost:5770 (synchronous): stopped
44 49 Erik Blaufuss
45 1 John Freeman
46 73 John Freeman
If RunControl is running, and at some point DAQInterface was running but has since been killed:
47 73 John Freeman
48 73 John Freeman
lbnecontrol: running
49 73 John Freeman
daqint@localhost:5770 (synchronous): missing
50 73 John Freeman
51 91 John Freeman
(In this case, just restart DAQInterface -- how to do this is described shortly).
52 73 John Freeman
53 49 Erik Blaufuss
If RunControl is not running, you'll see something like:
54 1 John Freeman
55 49 Erik Blaufuss
(env)[lbnedaq@lbne35t-gateway01 lbnerc]$ lbnecmd check
56 49 Erik Blaufuss
check failed: '[Errno 111] Connection refused'.  Is lbnecontrol running?
57 1 John Freeman
58 1 John Freeman
59 61 John Freeman
To check whether the configuration manager is running, you can simply use Linux commands:
60 61 John Freeman
61 61 John Freeman
62 61 John Freeman
ps aux | grep -v grep | grep CfgMgrApp
63 61 John Freeman
64 61 John Freeman
65 91 John Freeman
This will either return info on CfgMgrApp (the actual name of the configuration manager process), or print nothing if it's not running. In fact, it's possible to use Linux commands to check the status of all three programs:
66 71 John Freeman
67 71 John Freeman
68 75 John Freeman
ps aux | grep -v grep | egrep -e lbnecontrol -e daqinterface -e CfgMgrApp
69 71 John Freeman
70 61 John Freeman
71 105 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. 
72 105 John Freeman
73 105 John Freeman
h3. Cleanup: killing RunControl, DAQInterface and the configuration manager
74 105 John Freeman
75 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:
76 105 John Freeman
77 105 John Freeman
kill <PID>
78 105 John Freeman
79 105 John Freeman
If daqinterface is killed externally, then if it was in any state other than "stopped" at the time (and it likely was, otherwise a hard reset would likely have been avoidable), 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
80 105 John Freeman
81 105 John Freeman
ps aux | grep -v grep | grep pmt.rb
82 105 John Freeman
83 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.
84 105 John Freeman
85 1 John Freeman
h3. Starting RunControl
86 49 Erik Blaufuss
87 49 Erik Blaufuss
To start RunControl (after loading environment as above):
88 60 John Freeman
89 104 John Freeman
rm -f /tmp/  # (This should only be necessary if RunControl software wasn't stopped cleanly)
90 49 Erik Blaufuss
lbnecmd launch
91 49 Erik Blaufuss
92 1 John Freeman
93 1 John Freeman
h3. Starting DAQInterface
94 1 John Freeman
95 61 John Freeman
To start DAQInterface (after loading environment as above), the basic command is:
96 1 John Freeman
97 82 John Freeman
daqinterface -n daqint -r 5570 -c localhost -H localhost -f <daqinterface file> &
98 1 John Freeman
99 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. 
100 82 John Freeman
101 82 John Freeman
If multiple users with different terminals wish to check the DAQ output, it is recommended to try:
102 1 John Freeman
103 82 John Freeman
stdbuf -oL daqinterface -n daqint -r 5570 -c localhost -H localhost -f <daqinterface file> >>~/DI.log 2>&1 &
104 1 John Freeman
105 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)
106 82 John Freeman
107 1 John Freeman
h3. Starting the configuration manager
108 1 John Freeman
109 86 John Freeman
Please see the "Starting up the CfgMgrApp on lbne35t-gateway01" section of Jon Paley's documentation here:
110 62 John Freeman
111 61 John Freeman
h1. Configuring and starting Runs
112 1 John Freeman
113 61 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 to its log file when transitions are complete:
114 49 Erik Blaufuss
115 49 Erik Blaufuss
Initialize transition complete; if running DAQInterface in the background, can press <enter> to return to shell prompt
116 61 John Freeman
117 1 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. 
118 1 John Freeman
119 94 John Freeman
h2.  Selecting a run configuration and DAQ components
120 49 Erik Blaufuss
121 1 John Freeman
*Before initializing or starting a DAQ run*, a configuration and set of DAQComponents must be selected.  This is done via RunControl.
122 1 John Freeman
123 49 Erik Blaufuss
h3. List and select a configuration:
124 1 John Freeman
125 62 John Freeman
To see the list of available configurations (queried from the configuration manager):
126 49 Erik Blaufuss
127 49 Erik Blaufuss
lbnecmd listconfigs
128 1 John Freeman
129 49 Erik Blaufuss
Will return a list of configs:
130 49 Erik Blaufuss
131 49 Erik Blaufuss
Available configs (Name : description)
132 1 John Freeman
133 49 Erik Blaufuss
demo : Pithy description
134 49 Erik Blaufuss
tmp1 : Pithy description
135 49 Erik Blaufuss
136 30 John Freeman
137 49 Erik Blaufuss
Current selected config: No Config
138 49 Erik Blaufuss
139 49 Erik Blaufuss
This lists all available configs, as well as the current selected config (Note, default config is "No Config").  You can then select a configuration:
140 49 Erik Blaufuss
141 49 Erik Blaufuss
lbnecmd setconfig demo
142 1 John Freeman
143 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.
144 1 John Freeman
145 49 Erik Blaufuss
h3. List and select DAQ components.
146 1 John Freeman
147 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
148 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.
149 38 John Freeman
150 1 John Freeman
To see the list of available DAQ components:
151 49 Erik Blaufuss
152 1 John Freeman
lbnecmd listdaqcomps
153 49 Erik Blaufuss
154 62 John Freeman
Will return a list of components available and selected (*Default* is ALL available components), e.g.:
155 1 John Freeman
156 49 Erik Blaufuss
{'available': {'component02': ['lbnedaq2', '5206'], 'component01': ['lbnedaq2', '5205']}}
157 49 Erik Blaufuss
{'selected': {'component02': ['lbnedaq2', '5206'], 'component01': ['lbnedaq2', '5205']}}
158 49 Erik Blaufuss
159 62 John Freeman
Shown are the available components 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:
160 49 Erik Blaufuss
161 49 Erik Blaufuss
lbnecmd setdaqcomps component01 component02
162 49 Erik Blaufuss
163 62 John Freeman
This will return "OK" if successful ("lbnecmd listdaqcomps" will show this in the "selected" row of components).  If the specified compnents are not known, an error is returned.
164 49 Erik Blaufuss
To change the list of available components, see below.
165 29 John Freeman
166 91 John Freeman
h2. Initializing, starting, stopping and terminating a Run
167 1 John Freeman
168 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:
169 1 John Freeman
170 49 Erik Blaufuss
lbnecmd check
171 1 John Freeman
172 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.
173 1 John Freeman
174 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:
175 1 John Freeman
176 1 John Freeman
lbnecmd init daq
177 1 John Freeman
178 1 John Freeman
179 49 Erik Blaufuss
Take DAQInterface from the "ready" to the "running" state, in order to begin taking data:
180 29 John Freeman
181 1 John Freeman
lbnecmd start daq
182 29 John Freeman
183 49 Erik Blaufuss
Note: the current run number is displayed when DAQ is in the running state using the "lbnecmd check" command:
184 49 Erik Blaufuss
185 49 Erik Blaufuss
lbnecmd check
186 49 Erik Blaufuss
lbnecontrol: running
187 49 Erik Blaufuss
Run number: 207
188 49 Erik Blaufuss
Run configuration: demo
189 1 John Freeman
190 49 Erik Blaufuss
daqint@localhost:5570 (synchronous): running
191 49 Erik Blaufuss
192 49 Erik Blaufuss
193 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:
194 22 John Freeman
195 21 John Freeman
lbnecmd pause daq
196 42 John Freeman
197 41 John Freeman
198 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:
199 48 John Freeman
200 48 John Freeman
lbnecmd resume daq
201 48 John Freeman
202 48 John Freeman
203 48 John Freeman
Halt the running of the DAQ, returning DAQInterface to the "ready" state from the "running" state:
204 48 John Freeman
205 48 John Freeman
lbnecmd stop daq
206 49 Erik Blaufuss
207 49 Erik Blaufuss
From the ready state, you can start a new run with the same configuration and DAQ components you originally selected. 
208 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:
209 1 John Freeman
210 1 John Freeman
211 1 John Freeman
lbnecmd terminate daq
212 1 John Freeman
213 67 Erik Blaufuss
214 67 Erik Blaufuss
If you want to stop all RunControl processes (known as "lbnecontrol"):
215 67 Erik Blaufuss
216 67 Erik Blaufuss
lbnecmd kill
217 67 Erik Blaufuss
218 67 Erik Blaufuss
After this, you will need to relaunch RunControl as above.
219 1 John Freeman
220 49 Erik Blaufuss
h2. After your DAQ run.
221 1 John Freeman
222 49 Erik Blaufuss
Once you've completed your run, there are a few things you can look at. 
223 48 John Freeman
224 76 John Freeman
h3. The DAQ log
225 76 John Freeman
226 83 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/. 
227 76 John Freeman
228 76 John Freeman
h3. The run record
229 76 John Freeman
230 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>. 
231 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. 
232 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. 
233 72 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. E.g.,
234 72 John Freeman
235 72 John Freeman
Config name: demo
236 72 John Freeman
Component #0: component01
237 72 John Freeman
Component #1: component02
238 72 John Freeman
lbne-artdaq commit: 13b523181a6f8ff6e78ede590d6372ed6193c79c
239 1 John Freeman
lbnerc commit: 288001cf015e1a763dbba482923fc7ac8f379ae6
240 1 John Freeman
/data/lbnedaq/config commit: 877e43fe3ad96991adf5d57dbfbdefb6300fde25
241 1 John Freeman
242 76 John Freeman
243 81 John Freeman
h3. Output of the Art modules
244 76 John Freeman
245 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.
246 76 John Freeman
247 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:
248 76 John Freeman
249 76 John Freeman
250 76 John Freeman
cd <lbne-artdaq basedir>
251 76 John Freeman
source setupLBNEARTDAQ
252 76 John Freeman
rawEventDump -s <rootfile> -n <max events>
253 76 John Freeman
254 76 John Freeman
255 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:
256 76 John Freeman
257 76 John Freeman
258 81 John Freeman
%MSG-i MF_INIT_OK:  art 01-Dec-2014 16:13:59 CST JobSetup 
259 76 John Freeman
Messagelogger initialization complete.
260 76 John Freeman
261 81 John Freeman
%MSG-i PathConfiguration:  art 01-Dec-2014 16:14:00 CST JobSetup 
262 76 John Freeman
Multiple end paths have been combined into one end path,
263 76 John Freeman
"end_path" since order is irrelevant.
264 76 John Freeman
265 76 John Freeman
266 81 John Freeman
01-Dec-2014 16:14:00 CST  Initiating request to open file /tmp/lbne35t_r000270_sr01_20141201T221127.root
267 81 John Freeman
01-Dec-2014 16:14:00 CST  Successfully opened file /tmp/lbne35t_r000270_sr01_20141201T221127.root
268 1 John Freeman
269 76 John Freeman
Package             |Version             |Timestamp           
270 81 John Freeman
artdaq-core         |v1_04_06            |01-Dec-2014 21:59:51 UTC
271 81 John Freeman
artdaq              |v1_12_04            |01-Dec-2014 22:01:57 UTC
272 81 John Freeman
lbne-artdaq         |v0_00_08            |01-Dec-2014 22:00:18 UTC
273 81 John Freeman
lbne-artdaq         |v0_07_00            |01-Dec-2014 22:02:57 UTC
274 76 John Freeman
275 81 John Freeman
Begin processing the 1st record. run: 270 subRun: 1 event: 1 at 01-Dec-2014 16:14:00 CST
276 76 John Freeman
277 81 John Freeman
DAQ......... | daq........... | TOY1................. | std::vector<artdaq::Fragment> | artdaq::Fragments.... | ...2
278 1 John Freeman
DAQAG....... | TriggerResults | ..................... | art::TriggerResults.......... | art::TriggerResults.. | ...-
279 76 John Freeman
280 81 John Freeman
Total products (present, not present): 8 (2, 6).
281 76 John Freeman
282 1 John Freeman
283 76 John Freeman
DAQAG....... | BuildInfo... | LbneArtdaq........... | std::vector<artdaq::PackageBuildInfo> | artdaq::PackageBuildInfos | ...4
284 76 John Freeman
285 76 John Freeman
Total products (present, not present): 1 (1, 0).
286 76 John Freeman
287 81 John Freeman
01-Dec-2014 16:14:00 CST  Closed file /tmp/lbne35t_r000270_sr01_20141201T221127.root
288 76 John Freeman
289 76 John Freeman
TrigReport ---------- Event  Summary ------------
290 76 John Freeman
TrigReport Events total = 1 passed = 1 failed = 0
291 76 John Freeman
292 76 John Freeman
TrigReport ------ Modules in End-Path: end_path ------------
293 76 John Freeman
TrigReport  Trig Bit#    Visited     Passed     Failed      Error Name
294 76 John Freeman
TrigReport     0    0          1          1          0          0 printBuildInfo
295 76 John Freeman
TrigReport     0    0          1          1          0          0 out1
296 76 John Freeman
297 76 John Freeman
TimeReport ---------- Time  Summary ---[sec]----
298 1 John Freeman
TimeReport CPU = 0.003361 Real = 0.003000
299 1 John Freeman
300 76 John Freeman
Art has completed and will exit with status 0.
301 76 John Freeman
302 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.
303 81 John Freeman
304 84 John Freeman
h1. Configuring DAQInterface: the DAQInterface configuration file
305 91 John Freeman
306 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:
307 1 John Freeman
308 1 John Freeman
309 100 John Freeman
lbne-artdaq: /data/lbnedaq/daqarea/lbne-artdaq-base/build_lbne-artdaq
310 91 John Freeman
311 1 John Freeman
PMT host: lbnedaq3
312 100 John Freeman
PMT port: 5400
313 1 John Freeman
314 49 Erik Blaufuss
pause before initialization: 5
315 49 Erik Blaufuss
316 49 Erik Blaufuss
# debug level can range from 0 to 3 (increasing order of verbosity)
317 49 Erik Blaufuss
debug level: 1
318 49 Erik Blaufuss
319 49 Erik Blaufuss
log directory:   /data/lbnedaq/daqlogs
320 49 Erik Blaufuss
321 91 John Freeman
record directory: /data/lbnedaq/run_records
322 49 Erik Blaufuss
323 101 John Freeman
disable configuration check: false
324 101 John Freeman
325 101 John Freeman
TDU XMLRPC port: 0
326 101 John Freeman
327 91 John Freeman
EventBuilder host: lbnedaq2
328 91 John Freeman
EventBuilder port: 5235
329 91 John Freeman
EventBuilder fhicl: /data/lbnedaq/fcl/EventBuilder_demo1.fcl
330 48 John Freeman
331 91 John Freeman
EventBuilder host: lbnedaq2
332 91 John Freeman
EventBuilder port: 5236
333 91 John Freeman
EventBuilder fhicl: /data/lbnedaq/fcl/EventBuilder_demo2.fcl
334 48 John Freeman
335 91 John Freeman
Aggregator host: lbnedaq2
336 91 John Freeman
Aggregator port: 5265
337 48 John Freeman
338 91 John Freeman
Aggregator host: lbnedaq2
339 1 John Freeman
Aggregator port: 5266
340 1 John Freeman
341 1 John Freeman
342 1 John Freeman
343 92 John Freeman
The meaning of these parameters is as follows:
344 92 John Freeman
345 92 John Freeman
* *lbne-artdaq* : the directory in which the desired build of lbne-artdaq to use is located
346 92 John Freeman
347 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
348 100 John Freeman
* *PMT port* : pmt.rb's port
349 92 John Freeman
350 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
351 92 John Freeman
352 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. 
353 92 John Freeman
354 93 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
355 93 John Freeman
356 93 John Freeman
* *record directory* : the directory to which metadata about the run (FHiCL documents used, DAQInterface configuration file used, etc.) gets sent
357 101 John Freeman
358 101 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. 
359 101 John Freeman
360 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":
361 49 Erik Blaufuss
362 53 John Freeman
After these individual parameters, one defines the EventBuilderMain and AggregatorMain artdaq processes. Specifically, an EventBuilderMain is defined in three lines, where each line should contain "EventBuilder", and define the host and port on which the EventBuilderMain will run (to run an artdaq process on the same host as you're on, use "localhost") as well as the FHiCL document used to initialize the EventBuilderMain. AggregatorMain is defined similarly, using the token "Aggregator", but without the FHiCL document supplied, as this is supplied by the choice of configuration in the configuration manager. Best practice is to place the EventBuilderMain's FHiCL documents in the /data/lbnedaq/fcl directory. Please note that the order of processes matters, and that they should be listed front-end to back-end, i.e., EventBuilders should appear before Aggregators.
363 49 Erik Blaufuss
364 57 John Freeman
h1. Adding new configurations to RunControl
365 57 John Freeman
366 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. 
367 68 John Freeman
368 91 John Freeman
As of 11/20/14, the FHiCL documents associated with a given configuration are edited within the directory
369 57 John Freeman
370 57 John Freeman
371 57 John Freeman
372 57 John Freeman
where "named_configuration" would be the name of the configuration, in this example. Within this directory, the following files are expected:
373 57 John Freeman
* Aggregator1.fcl and Aggregator2.fcl, used to initialize the two AggregatorMain processes in the DAQ system
374 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")
375 59 John Freeman
376 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.
377 59 John Freeman
378 1 John Freeman
 event_builder_count: PLACEHOLDER
379 59 John Freeman
380 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.
381 1 John Freeman
382 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
383 68 John Freeman
384 68 John Freeman
git log
385 68 John Freeman
386 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:
387 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:
388 68 John Freeman
389 68 John Freeman
# On branch master
390 68 John Freeman
# Changes to be committed:
391 68 John Freeman
#   (use "git reset HEAD <file>..." to unstage)
392 68 John Freeman
393 68 John Freeman
#	new file:   helloworld/Aggregator1.fcl
394 68 John Freeman
#	new file:   helloworld/Aggregator2.fcl
395 68 John Freeman
#	new file:   helloworld/component01_hw_cfg.fcl
396 68 John Freeman
#	new file:   helloworld/component02_hw_cfg.fcl
397 68 John Freeman
398 68 John Freeman
399 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.:
400 68 John Freeman
401 1 John Freeman
git commit -m "JCF: helloworld: This configuration does not exist in the actual repo, it's simply used for documentation purposes"
402 68 John Freeman
403 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. 
404 68 John Freeman
405 68 John Freeman
Now, make sure that the commit took place correctly by running
406 68 John Freeman
407 68 John Freeman
git diff HEAD
408 68 John Freeman
409 68 John Freeman
If your commit is at the head of the master branch, you should see no output; additionally, if you run
410 1 John Freeman
411 68 John Freeman
git log
412 68 John Freeman
413 69 John Freeman
you should be able to see your commit at the top.
414 57 John Freeman
415 79 John Freeman
* Finally, make sure to push your change to the central repository; to do this, simply execute
416 79 John Freeman
417 79 John Freeman
git push origin
418 79 John Freeman
419 79 John Freeman
420 79 John Freeman
and now, if you run 
421 79 John Freeman
422 79 John Freeman
423 79 John Freeman
git diff origin/master
424 79 John Freeman
425 79 John Freeman
426 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. 
427 79 John Freeman
428 56 Erik Blaufuss
h1. Adding new DAQ Components to RunControl
429 49 Erik Blaufuss
430 49 Erik Blaufuss
The list of available DAQComponents (maps to BoardReader processes) is maintained by RunControl in the file:
431 49 Erik Blaufuss
432 49 Erik Blaufuss
433 18 John Freeman
434 55 Erik Blaufuss
Each entry (name: host port) defines:
435 55 Erik Blaufuss
* name - name of the component, maps to a <name>_hw_cfg.fcl in CfgMgr's configuration directory
436 49 Erik Blaufuss
* host - hostname where BoardReader process will be started
437 49 Erik Blaufuss
* port - XMLRPC port to be used, must be unique and used by other processes.
438 18 John Freeman
439 49 Erik Blaufuss
For example:
440 49 Erik Blaufuss
441 49 Erik Blaufuss
component01: lbnedaq2 5205
442 49 Erik Blaufuss
component02: lbnedaq2 5206
443 49 Erik Blaufuss
444 49 Erik Blaufuss
Has two components (component01 and component02) both running on lbnedaq2 on ports 5205 and 5206.
445 27 John Freeman
446 49 Erik Blaufuss
h1.  Troubleshooting and FAQ
447 28 John Freeman
448 49 Erik Blaufuss
h2.  Common RunControl issues
449 27 John Freeman
450 49 Erik Blaufuss
h3. How can I get a list of all RunControl commands?
451 1 John Freeman
452 49 Erik Blaufuss
453 49 Erik Blaufuss
lbnecmd help
454 49 Erik Blaufuss
455 50 Erik Blaufuss
will list all available commands for RunControl with some details for help.  
456 50 Erik Blaufuss
457 1 John Freeman
h3.  No real configurations are listed by RunControl
458 45 John Freeman
459 49 Erik Blaufuss
If you run "lbnecmd listconfigs" and see something like:
460 45 John Freeman
461 49 Erik Blaufuss
Available configs (Name : description)
462 49 Erik Blaufuss
463 49 Erik Blaufuss
dummy : Dummy description
464 45 John Freeman
465 49 Erik Blaufuss
Instead of your expected configurations, RunControl is not able to connect to CfgMgr.  Please make sure it's running (
466 1 John Freeman
467 49 Erik Blaufuss
h2.  Common DAQInterface issues
468 49 Erik Blaufuss
469 49 Erik Blaufuss
h3.  *Error handling*
470 49 Erik Blaufuss
471 49 Erik Blaufuss
As of this writing (11/14/14) certain potential problems have been anticipated and are handled within DAQInterface. These problems include:
472 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
473 49 Erik Blaufuss
# During periodic checks, one or more artdaq processes expected to exist are not found
474 49 Erik Blaufuss
475 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). 
476 49 Erik Blaufuss
477 84 John Freeman
h3. *Your change to the DAQInterface configuration file or the code doesn't seem to do anything*
478 49 Erik Blaufuss
479 1 John Freeman
Make sure you kill the existing daqinterface process and restart it
480 49 Erik Blaufuss
481 54 John Freeman
h3. *On the initial transition ("lbnecmd init daq"), you see "error: [Errno 111] Connection refused"*
482 49 Erik Blaufuss
483 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.
484 54 John Freeman
485 49 Erik Blaufuss
h3. *On the initial transition, you see a regularly updating printout saying "Waiting for all processes to be launched"*
486 1 John Freeman
487 1 John Freeman
Seeing one or two of these is fine. If, after several seconds, something like the following
488 1 John Freeman
489 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)
490 1 John Freeman
491 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 
492 1 John Freeman
493 1 John Freeman
ps aux | grep -v grep | grep pmt.rb 
494 51 John Freeman
495 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.
496 77 John Freeman
497 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*
498 1 John Freeman
499 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.