Suggestions on how to deal with top_block?

Hello,
I am new to GNU radio. I am trying to make modifications in
benchmark_rx.py, such that when there is keyboard interrupt, it will
call
benchmark_tx.py. While doing this, I got an error which read multiple
instances of top_block are not allowed. I read the previous posts, and
am
aware this a GNU radio defect. However, I was wondering if there is any
way
of terminating the top_block instance of benchmark_rx before
benchmark_tx is
called, when there is a key board interrupt, so that this problem would
not
arise? Thanks.

Prasanna.

View this message in context:
http://www.nabble.com/Suggestions-on-how-to-deal-with-top_block---tp18932035p18932035.html
Sent from the GnuRadio mailing list archive at Nabble.com.

On Mon, Aug 11, 2008 at 12:30 PM, call5_99 [email protected] wrote:

   I am new to GNU radio. I am trying to make modifications in

benchmark_rx.py, such that when there is keyboard interrupt, it will call
benchmark_tx.py. While doing this, I got an error which read multiple
instances of top_block are not allowed. I read the previous posts, and am
aware this a GNU radio defect. However, I was wondering if there is any way
of terminating the top_block instance of benchmark_rx before benchmark_tx
is
called, when there is a key board interrupt, so that this problem would not
arise? Thanks.

You can use the Python ‘del’ operator to force the top block instance to
go
out of scope when you want it to.

This issue will go away with the release of 3.2 (and on the development
trunk prior to that).

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