Fragment latency tracking
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.
#1 Updated by Eric Flumerfelt over 1 year 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.
Add forwarding methods to Fragment for touch, atime, and getLatency
Add branch to artdaq with corresponding metrics/TRACEs and latency updates