"Catching" end of flowgraph execution with GUI

Hi all (again),

is there any way to catch that my flowgraph has finished execution, to
reconfigure it after that and to be able to watch signals in GUI?

In my application I I would like to set some start and end values and to
press some kind of start button. After that flowgraph runs for the first
set of config parameters and after the execution is finished, it should
reconfigure itself and restart it for the second set of parameters, and
so
on … Meanwhile I would like to watch some signals in GUI.

I see that top_block_gui class calls infinite main loop and then it
blocks
there. I suppose that in order to acomplish above stated tast, I would
need
some kind of callback on flowgraph execution end. Is it possible to make
something like this?

Thanx,

Hi Nemanja,
typically, clicking your “start” button would spawn a new thread, in
which you top_block.start(), .stop() and .wait(); after wait returns,
you would then use whatever multithreading framework you’re using to
notify the threads that need to know.
GNU Radio is not very callback-oriented, i.e. there’s no “hooks” in the
scheduler – typically, you use “active” things like message passing to
hand information around.

Greetings,
Marcus

I had a similar problem recently. My solution was to subclass the
flowgraph adding the required functionality. Check out the
_top_block_waiter class in top_block.py. You can reimplement that logic
to e.g. add a time-out the the wait() call on the event or have a
callback executed.

Sebastian

On 05/05/2015 02:00 PM, Nemanja S. wrote:

in GUI.

I see that top_block_gui class calls infinite main loop and then it
blocks there. I suppose that in order to acomplish above stated tast,
I would need some kind of callback on flowgraph execution end. Is it
possible to make something like this?

Thanx,


Nemanja Savić


Karlsruhe Institute of Technology (KIT)
Communications Engineering Lab (CEL)

Dipl.-Ing. Sebastian Koslowski
Research Associate

Kaiserstraße 12
Building 05.01
76131 Karlsruhe, Germany

Phone: +49 721 608-46275
Fax: +49 721 608-46071
Email: [email protected]
Web: http://www.cel.kit.edu/

KIT – University of the State of Baden-Wuerttemberg and National
Research Center of the Helmholtz Association

Hi all guys,

I understand more or less what you are suggesting, although I am not
familiar with any multithreading framework, but at least I could ask
somebody here in the house. The problem is following, as I described in
my
other (recent :)) posts:

I have top block which consists of two flowgraphs, ie. tx path and rx
path.
Tx path transmitts limited number of frames and then stops, but RX
continues to work, which means that top block will also never stop. I
want
to be able to stop also RX path after the TX has finished. For this
reason
I don’t know how to catch that TX has finished and to proceed with
stopping
RX.

Best and thanx,
Nemanja

On Tue, May 5, 2015 at 8:10 PM, Koslowski, Sebastian (CEL) <

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