Project

General

Profile

Feature #15013

Allow artdaq to use other data-transfer mechanisms

Added by Eric Flumerfelt over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Start date:
01/11/2017
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Experiment:
-
Co-Assignees:
Duration:

Description

artdaq has long used MPI exclusively for data transfer. However, some experiments may have other requirements, or use architectures for which MPICH is unavailable. We should generalize the TransferPlugin interface and create manager classes that replace RHandles and SHandles that use the TransferPlugins to move data.


Subtasks

Support #15080: Remove now-unneccessary FHiCL parameters from AggregatorCore and EventBuilderCoreClosedEric Flumerfelt

Support #15081: Create test for DataReceiverManager and DataSenderManagerClosedEric Flumerfelt

History

#1 Updated by Eric Flumerfelt over 3 years ago

  • Status changed from New to Closed
  • Target version changed from 577 to v2_00_00
  • % Done changed from 90 to 100

artdaq/DAQrate/DataSenderManager and DataReceiverManager.
DataSenderManager currently sends data round-robin to the configured destinations.
DataReceiverManager polls its configured sources, and will stop polling a given source if it gets too far ahead (configurable).



Also available in: Atom PDF