Hi Glen,
One other possible approach could be to separate your processing flowgraph
from the display/GUI flowgraph. This could be done with a combo of ZMQ
blocks, the Parameter block and XMLRPC blocks.
Depending on your data rates, this might not work so great and is a bit
wasteful of CPU
On 11/14/2019 11:52 AM, Glen I Langston wrote:
Hi Amr,
Thanks for your suggestion.
However when I select no-gui, then all the QT blocks go RED in my designs in
gnuradio-companion.
I was hoping that they would instead just go quiet and use the default values.
I can, of course, just delete
It's a bit wasteful from a CPU cycles standpoint, but you can run your
flowgraph unchanged from the command line using xvfb, and no graphical
output will be displayed.
Nick
On Thu, Nov 14, 2019, 8:53 AM Glen I Langston
wrote:
> Hi Amr,
>
> Thanks for your suggestion.
>
> However when I select
Hi Glen,
On Thu, 2019-11-14 at 11:52 -0500, Glen I Langston wrote:
> Hi Amr,
>
> Thanks for your suggestion.
>
> However when I select no-gui, then all the QT blocks go RED in my designs in
> gnuradio-companion.
>
> I was hoping that they would instead just go quiet and use the default values.
Hi Amr,
Thanks for your suggestion.
However when I select no-gui, then all the QT blocks go RED in my designs in
gnuradio-companion.
I was hoping that they would instead just go quiet and use the default values.
I can, of course, just delete all the QT blocks, but then when going back
to
Hi Glen,
In the top right corner of the flow you will see the flow properties box.
In there you can disable the GUI. You can then run your python file
directly, or even call the created class object from another file (have a
look inside the main function to see how the flow is instantiated). You
