Feature #22535
Idea #22529: Support the (proto)DUNE DFO Model in artdaq
RoutingNetOutput plugin: A version of BinaryNetOutput that receives Routing Tokens
0%
Description
Part of the DFO infrastructure is a DataReceiver application (similar to EventBuilder, DataLogger, and Dispatcher), which receives data from the software triggering system, and determines the destinations on an event-by-event basis.
This could be accomplished by a version of BinaryNetOutput which uses a TokenReceiver class and RoutingPolicy to determine where to send data (triggering Requests to pull-mode BoardReaders).
History
#1 Updated by Kurt Biery 13 days ago
- File artdaqBranches_07Jun2019.pptx added
I haven't actually started working on the RoutingNetOutput module, but I wanted to capture some diagrams that show the branches that will likely feed into this.
Please see the attached file.
#2 Updated by Kurt Biery 13 days ago
- File deleted (
artdaqBranches_07Jun2019.pdf)
#3 Updated by Kurt Biery 13 days ago
#4 Updated by Kurt Biery 8 days ago
I've created working/22535_protoDFO_testing branches in both that artdaq_core and artdaq repositories. The merges shown in the attached slides have been done as part of creating these branches.
In addition, I've started modifying the code on this branch in the artdaq repo to start demonstrating the prototype DFO functionality. (for example, adding the RoutingNetOutput_module.)
There are lots of questions about how to handle things that I'm deferring, for now, in order to have something to test at protoDUNE, and of course, we'll need to come back to those questions.
#5 Updated by Kurt Biery 8 days ago
I've also created a working/22535_protoDFO_testing branch in the artdaq-utilities-daqinterface repo with tentative changes to DAQInterface to support the RoutingNetOutput_module.
#6 Updated by Kurt Biery about 4 hours ago
Uploading a new file with an updated picture of the branches (added working/22535_protoDFO_pduneHacks).