Hi Marcus,
Thank you for your patient replies. Last question.
>>Your block is asked "I'd like to ask you to produce 512 items. How much
input do you need?".
>>If your block then says "I need 400 items",
This means that for the block to output 512 items it needs 400 items in the
input.
>>no matt
Hi Anil,
On 05/29/2015 09:07 PM, Anil Kumar Yerrapragada wrote:
> Hi Marcus,
>
> Thanks for the explanation, it is very clear.
>
> But is there a way to keep track of time elapsed across *consecutive*
> work calls?
well, you have the nitems_read() method, which, assuming you have a
constant samp
Hi Marcus,
Thanks for the explanation, it is very clear.
But is there a way to keep track of time elapsed across *consecutive* work
calls?
Like I said in the first post in this thread, if I have a sliding window
based energy detect. Samples keep coming in, but at some point I will have
to say, r
Hi Anil,
On 05/29/2015 04:29 AM, Anil Kumar Yerrapragada wrote:
> >>Or is there a way to make sure that the in-buffer gets updated
> multiple times within the same work call?
>
> Will placing the work function inside a while 1 do the trick?
Never do that. Your job as GR user is to write the work()
>>Or is there a way to make sure that the in-buffer gets updated multiple
times within the same work call?
Will placing the work function inside a while 1 do the trick? But I guess
the issue with that is, as long as data is available, the scheduler calls
work function again and again anyway.
I'm
Hi
I'm writing a custom block in python. The application goes like this:
I specify the minimum number of samples I need by using the forecast
function. This ensures that I have that many samples available in the
in-buffer of the block every time work is called. Once I have as many
samples as I ne
