[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Gnuradio life cycle

From: Daniel Andres Palacios
Subject: Re: [Discuss-gnuradio] Gnuradio life cycle
Date: Thu, 13 Jun 2019 11:19:08 -0500

thank you, that definitely helps

On Tue, Jun 11, 2019 at 12:46 PM Müller, Marcus (CEL) <address@hidden> wrote:
Hi Daniel,

no, that's not right.

In your program, whatever that is, if it wants to use GNU Radio:

You set up a bunch of blocks – to even instantiate them, their
constructors must return – and then tell the GNU Radio top_block to
connect them. After you've done with that, you tell the top_block to
run() or start() (and wait() until finished).

That in turn allocates all the buffers between blocks, and then calls
every block's start() method (most blocks you'll see don't even
implement that) to make the block "ready".

After that, the scheduler starts doing its thing, which is calling all
the blocks' work() (or general_work()) methods, whenever there's new
input for a block and/or enough output space.

Maybe [1] helps a bit.

Best regards,

[1] https://www.gnuradio.org/blog/2017-01-05-buffers/
On Tue, 2019-06-11 at 12:30 -0500, Daniel Andres Palacios wrote:
> Hello to everyone.
> Could somebody explain me what is the life cycle of a gnuradio program? I understand that all the action occurs in the constructor of the main class. Am I right?
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Daniel Andrés Palacios Carabalí
Student of Telemathics engineering
Icesi University- Cali, Colombia
Estudiante de Ingeniería Telemática
Universidad Icesi. - Cali, Colombia

reply via email to

[Prev in Thread] Current Thread [Next in Thread]