You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the only real hooking into another dataflow infrastructure is in gr-pothos, which hacks in the block_executor to put a GNU Radio block inside a Pothos block. This approach is likely incompatible with other dataflow infrastructures. The idea here would be to put another dataflow toolkit's topology equivalent inside a Pothos::Topology and each of its blocks inside a Pothos::Block subclass. Connections between blocks would be done by overriding the _connect and _disconnect calls inside Pothos::Topology.
Connections between Pothos blocks don't do anything with buffers, and the Pothos blocks have getters and setters to hook into the underlying block's getters and setters and expose them as Pothos block functions (I don't know the implications with the scheduler here). There would be specific input and output blocks to pass Pothos buffers to and from this other toolkit.
I'm trying out this idea locally with an improved version of the GNU Radio RFNoC stuff linked above.
The text was updated successfully, but these errors were encountered:
Inspired by: https://github.com/gnuradio/gnuradio/blob/master/gr-uhd/examples/grc/rfnoc_radio_ddc.grc
Currently, the only real hooking into another dataflow infrastructure is in gr-pothos, which hacks in the block_executor to put a GNU Radio block inside a Pothos block. This approach is likely incompatible with other dataflow infrastructures. The idea here would be to put another dataflow toolkit's topology equivalent inside a
Pothos::Topology
and each of its blocks inside aPothos::Block
subclass. Connections between blocks would be done by overriding the_connect
and_disconnect
calls insidePothos::Topology
.Connections between Pothos blocks don't do anything with buffers, and the Pothos blocks have getters and setters to hook into the underlying block's getters and setters and expose them as Pothos block functions (I don't know the implications with the scheduler here). There would be specific input and output blocks to pass Pothos buffers to and from this other toolkit.
I'm trying out this idea locally with an improved version of the GNU Radio RFNoC stuff linked above.
The text was updated successfully, but these errors were encountered: