Re: How can you force the Scheduler to deliver appropriate vector size input

Thank you very much! George On Wed, Oct 26, 2022, 9:51 AM Marcus Müller wrote: > Haha! Perfect :) Glad you solved the issue! And absolutely no reason to be > sorry! > > On 26.10.22 17:04, George Edwards wrote: > > Hi Marcus, > > I have egg on my face! I messed up, Gnuradio works fine. I accident

Re: How can you force the Scheduler to deliver appropriate vector size input

Haha! Perfect :) Glad you solved the issue! And absolutely no reason to be sorry! On 26.10.22 17:04, George Edwards wrote: Hi Marcus, I have egg on my face! I messed up, Gnuradio works fine. I accidentally set one of the variables in the grc which contributes to the computation of the vector l

Re: How can you force the Scheduler to deliver appropriate vector size input

Hi Marcus, I have egg on my face! I messed up, Gnuradio works fine. I accidentally set one of the variables in the grc which contributes to the computation of the vector length incorrectly and made the size 496. Sometimes in the midst of these problems, we overlook the obvious. My mistake! Sorry fo

Re: How can you force the Scheduler to deliver appropriate vector size input

Good morning Marcus, Thanks for your response and sharing your thoughts. My understanding is that things should work exactly as you say. My flowgraph has two custom built OOT blocks. Based on my signal processing algorithms, one takes in vectors of size 200 and the other 448. The one that takes i

Re: How can you force the Scheduler to deliver appropriate vector size input

Hi George, I can't really follow. A block in GNU Radio has a *fixed* output item size. So, the Stream To Vector block *can* only produce items of size (448*sizeof(entry in the vector)). That can't change! Same with your block: it has an io_signature (you set it in the constructor), which fixe

Re: How can you force the Scheduler to deliver appropriate vector size input

Hello George, the input vector size is determined (more or less) by the forecast method. If the size is greater than you need, this is not a problem, you need to consume only the number of items you need. You will find the unconsumed items in the next buffer. The problem arises if you need a mini

How can you force the Scheduler to deliver appropriate vector size input

Hello GNURadio Community, I designed an OOT block to accept vectors of size 448 samples. In the flowgraph, my block is preceded a Stream-to-Vector block with the vector size set to 448 samples. My OOT block expects vector data that are of length 448 or multiple of 448 samples for signal processing