|Subject:||Re: [Discuss-gnuradio] zero ninput_items_required|
|Date:||Sat, 19 Oct 2013 10:35:17 +0200|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0|
Considering following flowgraph, assume your block is A, and assume all blocks work with the same itemsize.
good question, but basically, when running, when A is done with a run of work, it's thread notifies blocks "upstream" (B in this case) that it has consumed input items, making that space available for new output; GNU radio then calls forecast of B with a noutput_items to fill that space. However, if the upstream block B needs more input items than C has provided, GNU Radio will repeatedly reduce the number of samples it asks for until B needs less or equal samples as C has produced.
In your case, this only happens for 0 output items; thus your general_work gets called with 0 input items, as Martin already stated.
So what happens then? Since A has not provided any more output items for the blocks downstream, D can't do anything that it has not already been doing. The downstream part of the flowgraph stalls. Upstream part: Since GNU Radio has not been able to supply you with more than 0 input items, we can assume that the upstream part of the flowgraph is stuck, or done.
Therefore, execution ends here.
On 10/18/2013 03:19 PM, Nemanja Savic wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|