Project

General

Profile

Feature #22615

Fragment latency tracking

Added by Eric Flumerfelt 29 days ago. Updated 7 days ago.

Status:
Work in progress
Priority:
Normal
Category:
-
Target version:
-
Start date:
05/21/2019
Due date:
% Done:

0%

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

Description

The Fragment class should contain information about node-measured wall-clock time in order to help diagnose the latencys between the various hand-offs of Fragments in an artdaq system. This information should be part of the header, possibly as two 32-bit words consisting of seconds and nanoseconds. Fragment should also provide methods for appropriate access of these fields, such as "touch", "atime", and "GetLatency".

Measurement of the Fragment latency should be done on the receive side of each application boundary, i.e. in DataReceiverManager, SharedMemoryReader, and ArtdaqInput. Appropriate metrics, TRACE messages and warnings should be output.

History

#1 Updated by Eric Flumerfelt 28 days ago

I've started the first part by branching off of feature/FragmentValidHeaderField, which already contained a new version of RawFragmentHeader.

The new branch is artdaq-core:feature/22615_RawFragmentHeader_LatencyTracking.

Still TODO:
Add forwarding methods to Fragment for touch, atime, and getLatency
Add branch to artdaq with corresponding metrics/TRACEs and latency updates

#2 Updated by Eric Flumerfelt 28 days ago

  • Assignee set to Eric Flumerfelt
  • Status changed from New to Work in progress

#3 Updated by Eric Flumerfelt 7 days ago

This branch requires the artdaq-core_Utilities library to be included in Overlay libraries. artdaq-core-demo:feature/22615_IncludeLibrary has this change.



Also available in: Atom PDF