newsched
newsched copied to clipboard
The GNU Radio 4.0 Runtime Proof Of Concept
For some reason, when QT is enabled in a flowgraph, the connect method returns None, so custom buffers can't be added
Please suggest blocks that should be added to find issues and prove out the design - ZMQ - [x] PUSH/PULL - [x] PUB/SUB - [x] REQ/REP - Network - [...
The goal of this feature is to setup flowgraphs that can span multiple nodes. A first pass at this feature, or proof of concept I think involves the following: -...
Please add comments in this thread that should be changed as part of the coding standard.
Need mechanism to have a base block defined in YAML, then derived blocks that can inherit the callback methods Examples: - ZMQ blocks have common base
After the flowgraph gets partitioned, print a summary of what blocks live where, which threads, domain adapters, etc. This will probably require more intelligent naming of things for display.
Lot's of design and thought needs to go into this - this was just experimentation with some autogenerated doc strings for the python bindings, and then some experimentation with sphinx.
GRC is very dependent on GNU Radio and I'd prefer to not have it in tree Signed-off-by: Josh Morman
Started down this path, hoping that we could have some default custom buffer for e.g. cuda blocks, but there is no support for the transfer_type which is not known at...
Since so much of the code is generated, including the public header files, doxygen doesn't make as much sense anymore Seems it would be feasible to: 1) have a docs/...