Bug #15541

transfer_to_dispatcher should not be required

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

Known Issues
Target version:
Start date:
Due date:
% Done:


Estimated time:
(Total: 0.00 h)


otsdaq is currently using a Nx1x1 configuration, and therefore would like to not have a transfer_to_dispatcher block in their configuration. However, this results in a configuration error.

It would be good if this configuration parameter was optional, or rolled into a destinations: {} block in order to support multiple dispatchers.


Feature #15542: Allow configuration of multiple dispatchersClosedJohn Freeman

Feature #15543: Create "null" transfer pluginClosedEric Flumerfelt

Associated revisions

Revision fb0ef705 (diff)
Added by John Freeman over 3 years ago

JCF: add support for systems w/ artdaq v2 not using a dispatcher - will use this for Redmine Issue #15541

Revision a4aa3ca3 (diff)
Added by John Freeman over 3 years ago

JCF: make it optional whether a data logger has a transfer plugin for sending data to a dispatcher defined- this is done in light of Redmine Issue #15541

Revision a5a74a16 (diff)
Added by John Freeman over 3 years ago

At this point in code development, the data logger has been tested to
successfully use a DataSenderManager object to send events to two
dispatchers. However, we're not yet done for a couple of reasons:

1) The DataSenderManager appears to not be non-blocking, which isn't
the behavior we typically want for the non-critical
data-logger-to-dispatcher path

2) There's an implicit requirement that a data sender exist, and a
dispatcher exist to receive events from the sender - in other words,
the work done for Issue #15541 is effectively undone (for now) in this
switch from transfer plugin to DataSenderManager

3) There's not yet provision for round-robin sending of events to
multiple dispatchers - all events are broadcast to all dispatchers


#1 Updated by John Freeman over 3 years ago

  • Status changed from New to Resolved
  • Assignee set to John Freeman

artdaq commit a4aa3ca30e6cdb541a942ffef0ec6f0173cdceff addresses this issue. Also, I've modified DAQInterface so it can handle a scenario where we have one data logger and no dispatchers (DAQInterface commit fb0ef70539ca7ed5b8da1a46c2689cd73aa1790d) and have used this new commit of DAQInterface to successfully test that we can write out a root file using one data logger and no dispatchers both with and without transfer_to_dispatcher defined in the FHiCL, using the aforementioned artdaq commit.

#2 Updated by Eric Flumerfelt over 3 years ago

  • Status changed from Resolved to Closed
  • Target version changed from artdaq Next Release to artdaq v2_02_03

Also available in: Atom PDF