Project

General

Profile

Support #18797

Redesign of the timing associated to the trigger

Added by Gianluca Petrillo almost 2 years ago. Updated over 1 year ago.

Status:
Assigned
Priority:
Normal
Assignee:
Category:
Architecture
Target version:
-
Start date:
01/25/2018
Due date:
% Done:

0%

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

Description

detinfo::DetectorClocks relays an event trigger time.
The trigger time may be originating from reconstruction, that means that at the time of DetectorClocks configuration the trigger time might not be known yet, and become available only in the middle of the processing of the event. In that case an action needs to be triggered to update the service to deliver the newly reconstructed trigger.

This method is clumsy and introduces implicit sequencing.
A new feature of art 2.10 which allows a service to place a data product into the event might be used to design a data product based approach rather than a service based one.


Related issues

Blocked by LArSoft - Milestone #18796: Adopt art 2.10Closed01/25/2018

History

#1 Updated by Gianluca Petrillo almost 2 years ago

#2 Updated by Gianluca Petrillo almost 2 years ago

  • Subject changed from Redesign the timing associated to the trigger to Redesign of the timing associated to the trigger

#3 Updated by Lynn Garren almost 2 years ago

  • Status changed from New to Assigned

#4 Updated by Katherine Lato over 1 year ago

  • Assignee changed from Gianluca Petrillo to Kyle Knoepfel


Also available in: Atom PDF