Project

General

Profile

Idea #15749

Provide an option to DAQInterface in which it's not in charge of the artdaq processes

Added by John Freeman almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
artdaq-daqinterface
Target version:
-
Start date:
03/06/2017
Due date:
% Done:

100%

Estimated time:
20.00 h
Experiment:
-
Duration:

Description

Motivated by the desire on protoDUNE to use JCOP to possibly create, monitor, and/or send transitions to artdaq processes, after discussion with Kurt it's been decided that I should ensure that DAQInterface is written such that it's simple to use its functionality (primarily its ability to construct/bookkeep FHiCL documents) without requiring it to be in charge of the artdaq processes.


Related issues

Related to artdaq Utilities - Feature #15017: Create JCOP Metric PluginWork in progress01/05/2017

History

#1 Updated by John Freeman almost 3 years ago

#2 Updated by John Freeman over 2 years ago

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

Commit eaabbd04 handles this - basically, I've added the "manage_processes" member boolean to DAQInterface which, when true, relieves DAQInterface of having to directly deal with artdaq processes. This commit was used with JCOP during the just-finished protoDUNE DAQ Milestone Week 2.



Also available in: Atom PDF