Project

General

Profile

Feature #11416

Feature #11415: Implement Run and SubRun fragments

Input source must be able to aggregate products from (Sub)Run fragments

Added by Kyle Knoepfel almost 4 years ago. Updated over 3 years ago.

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

100%

Estimated time:
40.00 h
Spent time:
Scope:
Internal
Experiment:
-
SSI Package:
art
Duration:

Description

In order to support products from Run and SubRun fragments, the input source must be able to aggregate those products which were produced based on information from the events of that given subrun/run fragment.

History

#1 Updated by Kyle Knoepfel almost 4 years ago

  • Assignee set to Kyle Knoepfel

#2 Updated by Kyle Knoepfel almost 4 years ago

  • Status changed from New to Assigned

#3 Updated by Kyle Knoepfel almost 4 years ago

  • % Done changed from 0 to 80
  • Estimated time set to 40.00 h

#4 Updated by Kyle Knoepfel over 3 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 80 to 100

Run and SubRun products can now be aggregated across multiple Run or SubRun fragments. Any product that serves as a Run or SubRun product must be able to be aggregated. If an attempt to 'put' a Run or SubRun product is made and an aggregation-behavior does not exist for the type, a compile-time error is triggered with the diagnostic message:

art error: A (Sub)Run product must be able to be aggregated.
           Please add the appropriate 'void aggregate(T const&)' function
           to your class, or contact artists@fnal.gov.

Implemented across many commits. The merge commit of the develop branch into the feature branch is art:97485ee.

#5 Updated by Kyle Knoepfel over 3 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF