Is there a simple way to print out a list of what was connected into a
flow graph?
On Tue, May 20, 2008 at 12:09:27PM -0500, Brett L. Trotter wrote:
Is there a simple way to print out a list of what was connected into a flow
graph?
Not right now. However, just last night I was thinking about
something similar. Give me a day or so and I’ll put something
together.
Eric
On Tue, May 20, 2008 at 11:07 AM, Eric B. [email protected] wrote:
On Tue, May 20, 2008 at 12:09:27PM -0500, Brett L. Trotter wrote:
Is there a simple way to print out a list of what was connected into a flow
graph?Not right now. However, just last night I was thinking about
something similar. Give me a day or so and I’ll put something
together.
Eric–there is a dump() method on gr_flat_flowgraph objects currently
used for debugging. You can create a method on gr.top_block (exposed
via swig) that would call dump() on the d_ffg member.
–
Johnathan C.
Corgan Enterprises LLC
http://corganenterprises.com/
On Tue, May 20, 2008 at 11:14:18AM -0700, Johnathan C. wrote:
used for debugging. You can create a method on gr.top_block (exposed
via swig) that would call dump() on the d_ffg member.
Thanks! FYI, I opened it as ticket:245
Eric
Eric B. wrote:
something similar. Give me a day or so and I’ll put something
together.Eric–there is a dump() method on gr_flat_flowgraph objects currently
used for debugging. You can create a method on gr.top_block (exposed
via swig) that would call dump() on the d_ffg member.Thanks! FYI, I opened it as ticket:245
Eric
Most excellent. Thank you for the reply and the solution. Just debugging
some code and I think it’s just omission, but wanted to see if there’s
something connected higher up- it seemed being able to see what all was
hooked up would be handy.
Cheers and thanks!
Brett L. Trotter wrote:
Thanks! FYI, I opened it as ticket:245
Eric
Most excellent. Thank you for the reply and the solution. Just debugging
some code and I think it’s just omission, but wanted to see if there’s
something connected higher up- it seemed being able to see what all was
hooked up would be handy.
Cheers and thanks!
The latest trunk now has an added method to gr.top_block, dump(), that
will dump the runtime flattened flowgraph and connectivity. However, it
is only valid after calling start() on the top block, as that is when
the hierarchy gets flattened and pruned, to be passed to the scheduler.
In other words, you can replace:
tb.run()
…with:
tb.start() # Results in the hierarchy being flattened and pruned
tb.dump() # Dumps the flattened flowgraph to stdout
tb.wait() # Continues with the rest of what run() would have done
What would be better of course is a dump method that would show the
hierarchy, etc., as noted in Trac ticket #245.
Hello
Johnathan C. schrieb:
used for debugging. You can create a method on gr.top_block (exposed
via swig) that would call dump() on the d_ffg member.
I’ve written a small script to convert the output of dump() to the dot
format. If anyone is interested, it can be found under [1]. Some sample
output is at [2].
Regards, Andreas
[1] http://people.ee.ethz.ch/~andrmuel/files/gnuradio/dump2dot.py
[2] http://people.ee.ethz.ch/~andrmuel/files/gnuradio/dump.png
On Mon, May 26, 2008 at 01:51:39PM +0200, Andreas Müller wrote:
together.
Regards, Andreas[1] http://people.ee.ethz.ch/~andrmuel/files/gnuradio/dump2dot.py
[2] http://people.ee.ethz.ch/~andrmuel/files/gnuradio/dump.png
Thanks Andreas!
Eric