Running DAQ Interface » History » Version 60

John Freeman, 11/20/2014 05:01 PM

1 58 John Freeman
2 58 John Freeman
3 49 Erik Blaufuss
h1. Getting help
4 1 John Freeman
5 49 Erik Blaufuss
If you run into issues, or have questions, please contact:
6 49 Erik Blaufuss
* DAQInterface
7 49 Erik Blaufuss
** John Freeman -
8 49 Erik Blaufuss
* Run Control
9 49 Erik Blaufuss
** Erik Blaufuss -
10 1 John Freeman
11 49 Erik Blaufuss
h1. Starting DAQInterface and Run Control
12 49 Erik Blaufuss
13 49 Erik Blaufuss
DAQInterface is designed to be run, along with rest of the run control code, on, using the lbnedaq account.  These instructions will focus the use of DAQInterface on the gateway node.  If you need access to the account, please contact one of us.
14 49 Erik Blaufuss
The DAQInterface and RunControl software can also be run on the lbnedaqtest01 VM machine, please contact John Freeman at, for more details.
15 49 Erik Blaufuss
16 49 Erik Blaufuss
The installed code is located at /data/lbnedaq/scratch/DAQInterface/lbnerc. To get started, login and first setup the environment:
17 49 Erik Blaufuss
18 30 John Freeman
19 49 Erik Blaufuss
20 33 John Freeman
cd /data/lbnedaq/scratch/DAQInterface
21 1 John Freeman
source fireup
22 1 John Freeman
23 1 John Freeman
24 30 John Freeman
This will take you into the /data/lbnedaq/scratch/DAQInterface/lbnerc directory. It's a good idea to check whether lbnecontrol (the run control application) and/or DAQInterface (the component which intermediates between run control and artdaq processes) are already running; if they are, the instructions below won't work. To check this, you can try:
25 1 John Freeman
26 1 John Freeman
27 49 Erik Blaufuss
lbnecmd check
28 1 John Freeman
29 1 John Freeman
30 49 Erik Blaufuss
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 stopped:
31 49 Erik Blaufuss
32 49 Erik Blaufuss
(env)[lbnedaq@lbne35t-gateway01 lbnerc]$ lbnecmd check
33 49 Erik Blaufuss
lbnecontrol: running
34 49 Erik Blaufuss
daqint@localhost:5770 (synchronous): stopped
35 49 Erik Blaufuss
36 1 John Freeman
37 49 Erik Blaufuss
If RunControl is not running, you'll see something like:
38 1 John Freeman
39 49 Erik Blaufuss
(env)[lbnedaq@lbne35t-gateway01 lbnerc]$ lbnecmd check
40 49 Erik Blaufuss
check failed: '[Errno 111] Connection refused'.  Is lbnecontrol running?
41 49 Erik Blaufuss
42 1 John Freeman
43 49 Erik Blaufuss
h3. Starting RunControl
44 1 John Freeman
45 49 Erik Blaufuss
To start RunControl (after loading environment as above):
46 49 Erik Blaufuss
47 60 John Freeman
rm /tmp/
48 49 Erik Blaufuss
lbnecmd launch
49 49 Erik Blaufuss
50 1 John Freeman
51 49 Erik Blaufuss
h3. Starting DAQInterface
52 1 John Freeman
53 49 Erik Blaufuss
To start DAQInterface (after loading environment as above):
54 49 Erik Blaufuss
55 49 Erik Blaufuss
stdbuf -oL daqinterface -n daqint -r 5570 -c localhost -H localhost >>~/DI.log 2>&1 &
56 49 Erik Blaufuss
57 49 Erik Blaufuss
This will launch daqinterface in the background, with all messages being collected (appended to the bottom of...) in the file ~/DI.log  (The stdbuf -oL prevents and buffering of output to the file)
58 49 Erik Blaufuss
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. 
59 1 John Freeman
60 49 Erik Blaufuss
h3. Performing a hard reset of RunControl and DAQInterface
61 1 John Freeman
62 49 Erik Blaufuss
If needed, you can track down the process names and kill them explicitly to get a clean reset:
63 49 Erik Blaufuss
64 49 Erik Blaufuss
ps aux | grep -v grep | grep lbnecontrol
65 49 Erik Blaufuss
ps aux | grep -v grep | grep daqinterface
66 49 Erik Blaufuss
67 49 Erik Blaufuss
If these processes are running, it either means that someone else is using DAQInterface, or that someone else who's done with DAQInterface forgot to clean up. 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, the second field returned from "ps aux" is the process id (PID), use:
68 49 Erik Blaufuss
69 49 Erik Blaufuss
kill <PID>
70 49 Erik Blaufuss
71 1 John Freeman
72 49 Erik Blaufuss
h1. Configuring and starting Runs
73 1 John Freeman
74 49 Erik Blaufuss
All of these steps assume that the CfgMgr process is available.  To start this, please see the documentation here:
75 1 John Freeman
76 49 Erik Blaufuss
Now, you can take DAQ Interface 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 it's log file when transitions are complete:
77 49 Erik Blaufuss
78 49 Erik Blaufuss
Initialize transition complete; if running DAQInterface in the background, can press <enter> to return to shell prompt
79 49 Erik Blaufuss
80 49 Erik Blaufuss
Note that if a high "debug level" has been set, 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. 
81 1 John Freeman
82 49 Erik Blaufuss
h2.  Selecting a configuration and DAQcomponents
83 1 John Freeman
84 49 Erik Blaufuss
*Before initializing or starting a DAQ run*, a configuration and set of DAQComponents must be selected.  This is done via RunControl.
85 1 John Freeman
86 49 Erik Blaufuss
h3. List and select a configuration:
87 1 John Freeman
88 49 Erik Blaufuss
To see the list of available configurations (queried from CfgMgr):
89 49 Erik Blaufuss
90 49 Erik Blaufuss
lbnecmd listconfigs
91 1 John Freeman
92 49 Erik Blaufuss
Will return a list of configs:
93 49 Erik Blaufuss
94 49 Erik Blaufuss
Available configs (Name : description)
95 1 John Freeman
96 49 Erik Blaufuss
demo : Pithy description
97 49 Erik Blaufuss
tmp1 : Pithy description
98 49 Erik Blaufuss
99 30 John Freeman
100 49 Erik Blaufuss
Current selected config: No Config
101 49 Erik Blaufuss
102 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:
103 49 Erik Blaufuss
104 49 Erik Blaufuss
lbnecmd setconfig demo
105 49 Erik Blaufuss
106 49 Erik Blaufuss
This will return "OK" if successful (at "listconfigs" will show this as the current config).  If the specified configuration is not known, an error is returned.
107 1 John Freeman
108 49 Erik Blaufuss
h3. List and select DAQ components.
109 1 John Freeman
110 49 Erik Blaufuss
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 Boardreader processes
111 49 Erik Blaufuss
that read them out.   As an operator, you need to ensure that there are configuration files available in CfgMgr for the DAQ Components that you select here,
112 49 Erik Blaufuss
or DAQInterface will return an error.
113 38 John Freeman
114 49 Erik Blaufuss
To see the list of available DAQ components:
115 1 John Freeman
116 49 Erik Blaufuss
lbnecmd listdaqcomps
117 38 John Freeman
118 49 Erik Blaufuss
Will return a list of components available and selected (*Default* is ALL available components):
119 49 Erik Blaufuss
120 49 Erik Blaufuss
{'available': {'component02': ['lbnedaq2', '5206'], 'component01': ['lbnedaq2', '5205']}}
121 49 Erik Blaufuss
{'selected': {'component02': ['lbnedaq2', '5206'], 'component01': ['lbnedaq2', '5205']}}
122 49 Erik Blaufuss
123 49 Erik Blaufuss
Shown are the available components by name, along with the requested host/port to run the BoardReader process on. You can then select a list of DAQ components to use in the run:
124 49 Erik Blaufuss
125 49 Erik Blaufuss
lbnecmd setdaqcomps component01 component02
126 49 Erik Blaufuss
127 49 Erik Blaufuss
This will return "OK" if successful (at "lisdaqcomps" will show this as the current config).  If the specified compnents are not known, an error is returned.
128 49 Erik Blaufuss
To change the list of available components, see below.
129 29 John Freeman
130 49 Erik Blaufuss
h2. Configuring, starting, stopping and terminating a Run
131 1 John Freeman
132 49 Erik Blaufuss
For each of these transitions, please recall that while "lbnecmd <cmd>" returns very quickly, the actual command can take several seconds or minutes to happen.  Before issuing another command, be sure that the transition is complete by using the check command:
133 1 John Freeman
134 49 Erik Blaufuss
lbnecmd check
135 1 John Freeman
136 49 Erik Blaufuss
and ensure that the DAQ is, for example, in the "ready" state and not still in the "initializing" stage.
137 1 John Freeman
138 49 Erik Blaufuss
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 configuration:
139 1 John Freeman
140 1 John Freeman
lbnecmd init daq
141 1 John Freeman
142 1 John Freeman
143 49 Erik Blaufuss
Take DAQInterface from the "ready" to the "running" state, in order to begin taking data:
144 29 John Freeman
145 1 John Freeman
lbnecmd start daq
146 29 John Freeman
147 49 Erik Blaufuss
Note: the current run number is displayed when DAQ is in the running state using the "lbnecmd check" command:
148 49 Erik Blaufuss
149 49 Erik Blaufuss
lbnecmd check
150 49 Erik Blaufuss
lbnecontrol: running
151 49 Erik Blaufuss
Run number: 207
152 49 Erik Blaufuss
Run configuration: demo
153 1 John Freeman
154 49 Erik Blaufuss
daqint@localhost:5570 (synchronous): running
155 49 Erik Blaufuss
156 49 Erik Blaufuss
157 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:
158 22 John Freeman
159 21 John Freeman
lbnecmd pause daq
160 44 John Freeman
161 42 John Freeman
162 49 Erik Blaufuss
Resume the running of the DAQ, putting returning to the "running" state.  This will restart data taking to a new output file:
163 41 John Freeman
164 48 John Freeman
lbnecmd resume daq
165 48 John Freeman
166 48 John Freeman
167 48 John Freeman
Halt the running of the DAQ, returning DAQInterface to the "ready" state from the "running" state:
168 48 John Freeman
169 48 John Freeman
lbnecmd stop daq
170 48 John Freeman
171 49 Erik Blaufuss
From the ready state, you can start a new run with the same configuration and DAQ components you originally selected. 
172 49 Erik Blaufuss
*NOTE* To select a new configuration or DAQ component set, you must kill all ArtDAQ processes with the "terminate" command:
173 1 John Freeman
174 1 John Freeman
Now, return to the "stopped" state, killing all the artdaq processes:
175 1 John Freeman
176 1 John Freeman
lbnecmd terminate daq
177 1 John Freeman
178 1 John Freeman
179 49 Erik Blaufuss
h2. After your DAQ run.
180 1 John Freeman
181 49 Erik Blaufuss
Once you've completed your run, there are a few things you can look at. 
182 48 John Freeman
183 49 Erik Blaufuss
* A record of the DAQ's output will be saved in the subdirectory pmt/ relative to where you specified the output logfiles; thus in the example config.txt below, you'd find the output in /data/lbnedaq/daqlogs/pmt/. 
184 51 John Freeman
* Also, a record of the FHiCL documents sent to the artdaq processes and the docs/config.txt file will have been saved; as of this writing (11/12/14) the directory in which this can be found defaults to /data/lbnedaq/scratch/jcfree/TemporarySaveArea/<run number>, although as you might imagine the plan is to eventually change this directory. 
185 51 John Freeman
** PLEASE NOTE that there may be slight differences between the saved FHiCL documents and the FHiCL documents specified in config.txt and/or provided by the choice of configuration. The saved FHiCL document name is standardized to <processtype>_<host>_<port>_r<run number>.fcl, so, e.g, "Aggregator_lbnedaq2_5266_r192.fcl" would be the saved name of /data/lbnedaq/fcl/Aggregator_lbnedaq2_2.fcl, listed in the example config.txt file above, assuming datataking was performed in run 192. 
186 49 Erik Blaufuss
** 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. 
187 52 John Freeman
* Output of the Art modules. 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.
188 1 John Freeman
189 49 Erik Blaufuss
h1. Configuring DAQInterface
190 49 Erik Blaufuss
191 52 John Freeman
DAQInterface has some key information stored in a local configuration file (location and ports for EventBuilders, Aggregators, location of artDAQ, log level, etc). These can be changed while DAQInterface is not running,  It's expected that for normal operations, these should not need to changed too often. Assuming the processes aren't running, before getting started, take a look at the configuration file, found in docs/config.txt (relative to /data/lbnedaq/scratch/DAQInterface/lbnerc). 
192 49 Erik Blaufuss
It should look something like the following:
193 1 John Freeman
194 49 Erik Blaufuss
lbne-artdaq: /data/lbnedaq/scratch/DAQInterface/build_lbne-artdaq
195 1 John Freeman
196 49 Erik Blaufuss
PMT host: lbnedaq3
197 49 Erik Blaufuss
198 49 Erik Blaufuss
pause before initialization: 5
199 49 Erik Blaufuss
200 49 Erik Blaufuss
# debug level can range from 0 to 3 (increasing order of verbosity)
201 49 Erik Blaufuss
debug level: 1
202 49 Erik Blaufuss
203 49 Erik Blaufuss
log directory:   /data/lbnedaq/daqlogs
204 49 Erik Blaufuss
205 49 Erik Blaufuss
record directory: /data/lbnedaq/scratch/jcfree/TemporarySaveArea/
206 49 Erik Blaufuss
207 1 John Freeman
 EventBuilder host: lbnedaq2
208 48 John Freeman
 EventBuilder port: 5235
209 48 John Freeman
 EventBuilder fhicl: /data/lbnedaq/fcl/EventBuilder_demo1.fcl
210 48 John Freeman
211 48 John Freeman
 EventBuilder host: lbnedaq2
212 48 John Freeman
 EventBuilder port: 5236
213 48 John Freeman
 EventBuilder fhicl: /data/lbnedaq/fcl/EventBuilder_demo2.fcl
214 48 John Freeman
215 48 John Freeman
 Aggregator host: lbnedaq2
216 48 John Freeman
 Aggregator port: 5265
217 41 John Freeman
218 1 John Freeman
 Aggregator host: lbnedaq2
219 21 John Freeman
 Aggregator port: 5266
220 49 Erik Blaufuss
221 1 John Freeman
222 49 Erik Blaufuss
The "lbne-artdaq" parameter allows the user to set the directory in which the desired build of lbne-artdaq to use is located, the "PMT host" parameter is the host on which artdaq's process management tool script (pmt.rb, used by DAQInterface to launch and kill the artdaq processes) will run, and "log directory" is the directory to which lbne-artdaq's output will be sent. The "debug level" parameter 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. The "pause before initialization" parameter allows the user to set a pause, in seconds, between when the artdaq processes start and when they're initialized; it has been observed that a latency of a few seconds is needed for initialization to proceed correctly (though this is not always the case -- on lbne35t-gateway01, with a high setting for "debug level", a pause is not needed; the reason why "debug level" matters in this context is not yet understood).
223 49 Erik Blaufuss
224 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.
225 49 Erik Blaufuss
226 57 John Freeman
h1. Adding new configurations to RunControl
227 57 John Freeman
228 57 John Freeman
Adding a new configuration selectable from RunControl is quite simple. As of 11/20/14, the FHiCL documents associated with a given configuration are stored within the directory
229 57 John Freeman
230 57 John Freeman
231 57 John Freeman
232 57 John Freeman
where "named_configuration" would be the name of the configuration, in this example. Within this directory, the following files are expected:
233 57 John Freeman
* Aggregator1.fcl and Aggregator2.fcl, used to initialize the two AggregatorMain processes in the DAQ system
234 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")
235 57 John Freeman
236 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.
237 59 John Freeman
238 59 John Freeman
 event_builder_count: PLACEHOLDER
239 59 John Freeman
240 59 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. 
241 57 John Freeman
242 57 John Freeman
243 56 Erik Blaufuss
h1. Adding new DAQ Components to RunControl
244 49 Erik Blaufuss
245 49 Erik Blaufuss
The list of available DAQComponents (maps to BoardReader processes) is maintained by RunControl in the file:
246 49 Erik Blaufuss
247 49 Erik Blaufuss
248 18 John Freeman
249 55 Erik Blaufuss
Each entry (name: host port) defines:
250 55 Erik Blaufuss
* name - name of the component, maps to a <name>_hw_cfg.fcl in CfgMgr's configuration directory
251 49 Erik Blaufuss
* host - hostname where BoardReader process will be started
252 49 Erik Blaufuss
* port - XMLRPC port to be used, must be unique and used by other processes.
253 18 John Freeman
254 49 Erik Blaufuss
For example:
255 49 Erik Blaufuss
256 49 Erik Blaufuss
component01: lbnedaq2 5205
257 49 Erik Blaufuss
component02: lbnedaq2 5206
258 49 Erik Blaufuss
259 49 Erik Blaufuss
Has two components (component01 and component02) both running on lbnedaq2 on ports 5205 and 5206.
260 27 John Freeman
261 49 Erik Blaufuss
h1.  Troubleshooting and FAQ
262 28 John Freeman
263 49 Erik Blaufuss
h2.  Common RunControl issues
264 27 John Freeman
265 49 Erik Blaufuss
h3. How can I get a list of all RunControl commands?
266 1 John Freeman
267 49 Erik Blaufuss
268 49 Erik Blaufuss
lbnecmd help
269 49 Erik Blaufuss
270 50 Erik Blaufuss
will list all available commands for RunControl with some details for help.  
271 50 Erik Blaufuss
272 50 Erik Blaufuss
h3.  No real configurations are listed by RunControl
273 45 John Freeman
274 49 Erik Blaufuss
If you run "lbnecmd listconfigs" and see something like:
275 45 John Freeman
276 49 Erik Blaufuss
Available configs (Name : description)
277 49 Erik Blaufuss
278 49 Erik Blaufuss
dummy : Dummy description
279 45 John Freeman
280 49 Erik Blaufuss
Instead of your expected configurations, RunControl is not able to connect to CfgMgr.  Please make sure it's running (
281 1 John Freeman
282 49 Erik Blaufuss
h2.  Common DAQInterface issues
283 49 Erik Blaufuss
284 49 Erik Blaufuss
h3.  *Error handling*
285 49 Erik Blaufuss
286 49 Erik Blaufuss
As of this writing (11/14/14) certain potential problems have been anticipated and are handled within DAQInterface. These problems include:
287 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
288 49 Erik Blaufuss
# During periodic checks, one or more artdaq processes expected to exist are not found
289 49 Erik Blaufuss
290 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). 
291 49 Erik Blaufuss
292 49 Erik Blaufuss
h3. *Your change to docs/config.txt or doesn't seem to do anything*
293 49 Erik Blaufuss
294 1 John Freeman
Make sure you kill the existing daqinterface process and restart it
295 49 Erik Blaufuss
296 54 John Freeman
h3. *On the initial transition ("lbnecmd init daq"), you see "error: [Errno 111] Connection refused"*
297 49 Erik Blaufuss
298 1 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 docs/config.txt file. Empirically, it appears there needs to be a pause of at least 4 seconds on 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.
299 54 John Freeman
300 49 Erik Blaufuss
h3. *On the initial transition, you see a regularly updating printout saying "Waiting for all processes to be launched"*
301 49 Erik Blaufuss
302 1 John Freeman
Seeing one or two of these is fine. If, after several seconds, something like the following
303 1 John Freeman
304 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)
305 1 John Freeman
306 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 
307 1 John Freeman
308 1 John Freeman
ps aux | grep -v grep | grep pmt.rb 
309 1 John Freeman
310 51 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 docs/config.txt?), then try increasing the debug level in docs/config.txt for your next run-through, as this will likely shed light on the nature of the problem.