Project

General

Profile

Idea #24398

Separate Request Buffering from Request Receiving

Added by Eric Flumerfelt about 2 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Category:
-
Target version:
-
Start date:
05/12/2020
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Duration:

Description

In the current artdaq model, RequestReceiver is instantiated by CommandableFragmentGenerator and is responsible for receiving request as well as storing them and making them available to CFG upon request. In a more modular view of artdaq, the request receiving capability should be separated from the request storage, so that RequestReceiver could be replaced with a different implementation and not affect the CFG code.


Related issues

Related to artdaq - Idea #24508: Separate Fragment Buffering (and Request applying) from GeneratingResolved06/03/2020

History

#1 Updated by Eric Flumerfelt about 2 months ago

  • Status changed from New to Resolved

This has been implemented on artdaq:feature/24398_RequestReceiver_RequestBufferSeparation. There is a configuration change on artdaq-utilities-daqinterface:feature/24398_RequestReceiver_CfgChanges; all BoardReaders in pull mode need to set "receive_requests: true", similar to how EventBuilders must set "send_requests: true" if they intend to send requests.

#2 Updated by Eric Flumerfelt about 1 month ago

  • Related to Idea #24508: Separate Fragment Buffering (and Request applying) from Generating added


Also available in: Atom PDF