Project

General

Profile

Feature #22342

Allow users more control over which Metric levels go to which plugins

Added by Eric Flumerfelt over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Category:
artdaq-utilities
Start date:
04/09/2019
Due date:
% Done:

0%

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

Description

We have had several cases where users are interested in seeing a single metric being reported to a specific destination. It would be fairly easy to make it so that MetricPlugin supports more advanced specification of the levels that it is interested in.

Based on our experience with TRACE, providing a 64-bit bitmask will most likely be sufficient, though I will attempt to make a more transparent configuration interface that will work better with fhicl.

History

#1 Updated by Eric Flumerfelt over 1 year ago

Implementation on feature/22342_MetricPlugin_LevelMask, based on feature/22326_MetricPlugin_FixParameterDocumentation.

#2 Updated by Eric Flumerfelt over 1 year ago

  • Status changed from Work in progress to Resolved

I have tested this feature with MetricManager_t and MetricPlugin_t. For branch verification, it would probably be a good idea to exercise it in an artdaq_demo system.

#3 Updated by Ron Rechenmacher over 1 year ago

  • Status changed from Resolved to Reviewed

merged artdaq_utilities feature/22342_MetricPlugin_LevelMask and artdaq feature/22342_MoveMetricTestsToArtdaqUtilities into develop and tested.

#4 Updated by Eric Flumerfelt over 1 year ago

  • Target version set to artdaq_utilities v1_05_00
  • Status changed from Reviewed to Closed
  • Category set to artdaq-utilities

Also available in: Atom PDF