Running benchmark_rx.py in debugging mode

hi everyone,
Is there any way for me to run the benchmark_tx and
benchmark_rx.py files in debugging mode so that I can see the entire
flow
structure? I am curious to know the steps that take place from the
calling
of the python script to the point where the modulated symbols are
transmitted via the USB2.0.
Regards,
Amarnath

On Mon, Feb 22, 2010 at 3:55 AM, amarnath alapati
[email protected] wrote:

hi everyone,
Is there any way for me to run the benchmark_tx and
benchmark_rx.py files in debugging mode so that I can see the entire flow
structure? I am curious to know the steps that take place from the calling
of the python script to the point where the modulated symbols are
transmitted via the USB2.0.
Regards,
Amarnath

I’m not sure exactly what you mean by ‘debugging mode’. You can
attach a running flowgraph to gdb
(http://www.gnu.org/software/gnuradio/doc/howto-write-a-block.html#debugging),
but I would think that that’s lower level stuff than you are looking
for, and the multi-threaded scheduler makes it difficult to monitor
specific flows for a less-than-expert gdb user.

At the current point in time there doesn’t seem to be a way to ‘single
step’ through a flow graph and monitor the inputs and outputs, no
‘gnuradio debugger’ as it were. I think this would be a nice feature
to have, both in grc and as command line tool, but I think it’s a
pretty hard thing to implement given the current code.

You can turn on logging the benchmark_*x files which will give you the
modulation steps only, if that is what you are interested in. You
will have to view the log files with octave or matlab and synchronize
them yourself.

Jason

On Mon, Feb 22, 2010 at 07:34:01AM -0600, Jason U. wrote:

On Mon, Feb 22, 2010 at 3:55 AM, amarnath alapati
removed_email_addr[email protected] wrote:

hi everyone,
Is there any way for me to run the benchmark_tx and
benchmark_rx.py files in debugging mode so that I can see the entire flow
structure? I am curious to know the steps that take place from the calling
of the python script to the point where the modulated symbols are
transmitted via the USB2.0.
Regards,
Amarnath

You can turn logging on.

Try

$ benchmark_rx.py --help

You’ll have to look at the code to understand what’s in each log file.

Eric

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs