Hi all,
I'm investigating the factors behind the latency in my simple GRC flow
graph, I have a theory and I'd be grateful if someone can confirm it or
refute it.
Say I have a simple flow graph consisting of a file source connected to a
hardware sink.
My understanding: when I run the flow graph,
Thank you very much. We will try that.
Grace
On 4/24/23 09:36, Josh Morman wrote:
Do you have pygccxml and castxml installed on this machine? And if
so, are they recent versions (pygccxml >= 2.0)
When gr_modtool bind is called, pygccxml compiles the project headers
then scrapes the symbol i
Do you have pygccxml and castxml installed on this machine? And if so, are
they recent versions (pygccxml >= 2.0)
When gr_modtool bind is called, pygccxml compiles the project headers then
scrapes the symbol information to generate the python bindings. Not
finding memory.h sounds like an outdate
Hi, I am trying to port my OOTs from gr 3.8 to 3.10. Following the
porting guide and running "gr_modtool bind" work on all our machines
running 3.10 except one that is on 3.10.5 where block.h tries to include
memory.h which is missing. What's the best way to get around this
besides just copying
Hi,
I'm trying to understand gnuradio's logging.
So I setup a simple flowgraph
signal_source -> throttle-> add const-> time_sink.
To enable debug logging I have to set
[log]
debug_file = stderr
debug_level = debug
log_file = stdout
log_level = debug
in ~/.gnuradio/config.conf
or in $CMAKE_INS
