Hi Jeff,
Thank you very much!
George
On Thu, Apr 21, 2022 at 12:21 PM Jeff Long wrote:
> Right. Of course you can just use one loop of noutput_items * vlen
> iterations.
>
> Technically noutput_items says how many items you may write, not how many
> the scheduler is delivering (implying
Right. Of course you can just use one loop of noutput_items * vlen
iterations.
Technically noutput_items says how many items you may write, not how many
the scheduler is delivering (implying input). In a sync block, they are the
same though, unless you overwritten forecast().
On Thu, Apr 21,
Hi Jeff,
Thanks for your reply!
So let me make certain that I understand correctly your response where you
said there were 16*512 samples (8192 samples). So I take it that noutput_items
(which has alternating values of 15 and 16 when printed to the screen) tells
me the number of vectors of vlen
The item size is vlen * sizeof (type), so you are seeing 16 * 512 "samples".
On Wed, Apr 20, 2022 at 1:44 PM George Edwards
wrote:
> Hello GNURadio Community,
>
> I have written a C++ OOT "sync" block with vector input and vector output
> (data type float). I wrote a line in my program to print
Hello GNURadio Community,
I have written a C++ OOT "sync" block with vector input and vector output
(data type float). I wrote a line in my program to print the value of
noutput_items on each GRC flow graph iteration and it alternately prints
the values 15 and 16. This is surprising!!! I was
