[Top][All Lists]

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

Re: [Discuss-gnuradio] A question about function gr::block::set_history(

From: Kun Qian
Subject: Re: [Discuss-gnuradio] A question about function gr::block::set_history()
Date: Fri, 8 Aug 2014 09:54:11 -0700 (PDT)

2014-08-08 16:25 GMT+08:00 Lei [via GnuRadio] <[hidden email]>:
        Sorry to bother you.I have some confusions on general_work().
       1.What's the mechanism of the general_work()? I've no idea about how to
find the material on it,and the site of gnu radio has too little information on it.
The function general_work is the place where a block processes input items and generates output items according to its functionality (such as filter). Besides the functionality, you have to tell the invoker how many items from each input port are consumed by invoking function consume or consume_each and how many items for each output port are generated through return value.

       2.Is the method general_work()  called automatically ?It seems that the function can consume the data automatically.How or whether can I control the
execution of general_work()?

Exactly, general_work are all automatically invoked by gr-scheduler, one of the core component of gnuradio, which handles runtime stuff of whole flow graphs. So, you don't have to control the execution of general_work().

The following PDF gives a brief introduction about gr-scheduler, including general_work function:


        Thanks.Looking forward to your reply

If you reply to this email, your message will be added to the discussion below:
To unsubscribe from A question about function gr::block::set_history(), click here.

Qian Kun
School of Software, Tsinghua University
Tel: (+86)15201519125
Email: [hidden email]

View this message in context: Re: A question about function gr::block::set_history()
Sent from the GnuRadio mailing list archive at Nabble.com.

reply via email to

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