Project

General

Profile

Idea #11690

Possible changes to CommandableFragmentGenerator methods and sample child classes

Added by Kurt Biery over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
02/09/2016
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Duration:

Description

As part of the ICARUS/artdaq discussion on 09-Feb-2016 (https://cdcvs.fnal.gov/redmine/projects/artdaq/wiki/February_9_2016_discussion_notes), the following issue were noted:

  1. Do we want to make more of the protected methods in CommandableFragmentGenerator virtual? [start, stop, report?] [also see notes on slide 8 of the Google slides from 09-Feb]
  2. The samples that we provide in the demo should have all of the methods that we want users to consider included, even if they are empty. We should also include comments that talk about what can be done in each of them, etc. Also include relative path to CommandableFragGen so users can easily look at.

History

#1 Updated by Kurt Biery over 3 years ago

  • Target version changed from 575 to v1_12_15

#2 Updated by Kurt Biery over 3 years ago

  • Status changed from New to Resolved

start, stop, and stopNoMutex were made pure virtual, and child classes were updated appropriately.

pause, pauseNoMutex, resume, report, and reportSpecific were updated to print out a compiler message when the default (empty) implementation is no over-ridden.

These changes implement the scheme that we decided upon in our internal discussions.

#3 Updated by Eric Flumerfelt over 3 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF