Bug #739
Multiple end of run daq events for each spill
Status:
Rejected
Priority:
Low
Assignee:
Category:
RealData
Target version:
Start date:
12 October 2011
Due date:
% Done:
0%
Estimated time:
Workflow:
Description
Small thing, I noticed that there are 4 end_of_run daq events created by the test data set.
So I attached daq.out, where I switched off the actual unpacking of all the hardware (I just wanted to see the structure). Run by doing something like
./bin/analyze_data_offline.py -configuration_file config.py -output_json_file_name daq.out
Files
Updated by Rogers, Chris almost 12 years ago
- Status changed from Open to Rejected
After conversation with Yordan - this is correct behaviour in fact.