Project

General

Profile

Idea #24508

Separate Fragment Buffering (and Request applying) from Generating

Added by Eric Flumerfelt about 1 month ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
06/03/2020
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Duration:

Description

Currently, CommandableFragmentGenerator is responsible for both acquiring data from a FragmentGenerator plugin and storing that data until requested (as well as managing these buffers). This functionality can be separated, to allow for easier construction of applications which may not need the buffering/requesting functionality, or which do not need Fragment generators but do need request response functionality (e.g. art processes in a multi-layer system).


Related issues

Related to artdaq - Idea #24398: Separate Request Buffering from Request ReceivingResolved05/12/2020

History

#1 Updated by Eric Flumerfelt about 1 month ago

  • Related to Idea #24398: Separate Request Buffering from Request Receiving added

#2 Updated by Eric Flumerfelt about 1 month ago

  • Status changed from New to Resolved

#3 Updated by Eric Flumerfelt about 1 month ago

Changes are on the feature/24508_FragmentBuffer_fromCFG branches of artdaq and artdaq_demo. Since these branches derive from the #24398 branches, the artdaq_daqinterface branch feature/24398_RequestReceiver_CfgChanges is also required.



Also available in: Atom PDF