[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: |
Mon, 19 May 2014 08:48:54 -0700 (PDT) |
Thank you for your quick answer!
I think I get how gnuradio works with history from your slides:
1. When flowgraph starts, the read pointer of input buffer is set
history()-1 items back.
2. After calling work()/general_work() function, gnuradio scheduler get the
number of consumed items of that input buffer and move the read pointer
forward by that number. Then scheduler wait until next time calling
work()/general_work() function.
Is it right?
And I think I find the error. In gr::block::general_work(), the parameter
ninput_items equals to the *sum* of *noutput_items of previous block* and
*history()-1*, isn't it? I thought ninput_items equals to noutput_items of
previous block when I built the block.
--
View this message in context:
http://gnuradio.4.n7.nabble.com/A-question-about-function-gr-block-set-history-tp48313p48333.html
Sent from the GnuRadio mailing list archive at Nabble.com.