Project

General

Profile

Feature #20797

On run start and stop, DAQInterface should call a script to make working with TRACE buffers easier

Added by John Freeman about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
09/11/2018
Due date:
% Done:

100%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

In the context of protoDUNE, there's been a discussion of ways that DAQInterface can make it easier for users of TRACE to determine what happened during a particular run. The idea is essentially that at the start of a run, the TRACE buffer would get reset, and at the stop, the TRACE buffer would get saved.

Ron and I agreed that the best way to achieve this would be to have DAQInterface call a script on run start and run stop, passing it the list of nodes the artdaq processes are running on, the run number, and the name of the trace buffer. It could be the same script, accepting a boolean to tell it whether to execute start logic or stop logic. The advantage to this approach is "separation of concerns": DAQInterface is decoupled from the details of how exactly users want trace buffers to be dealt with on run start and stop.

History

#1 Updated by John Freeman about 1 year ago

  • Assignee set to John Freeman

#2 Updated by John Freeman about 1 year ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

DAQInterface v3_00_06f satisfies this issue. If it finds a script with the name /nfs/sw/control_files/trace/trace_control.sh, it will execute it on the start transition with arguments which look like, e.g.

/nfs/sw/control_files/trace/trace_control.sh /tmp/trace_dune-artdaq_artdaq_v3_02_01_testing --run 1001613 --transition start --node-list="np04-srv-001 np04-srv-002 np04-srv-011" 

...and similarly on the stop transition.



Also available in: Atom PDF