Re: How to force the decimation to schedule at least 16 output samples

2023-03-15 Thread Jeff Long
Actually min noutput items is used in block_executor, now that I trace it through a bit. But I'm glad you got something to work. On Wed, Mar 15, 2023 at 7:26 PM Jeff Long wrote: > Oh, right. I remember that whole conversation about that function doing > nothing. It got me again! > > On Wed, Mar

Re: How to force the decimation to schedule at least 16 output samples

2023-03-15 Thread Jeff Long
Oh, right. I remember that whole conversation about that function doing nothing. It got me again! On Wed, Mar 15, 2023 at 3:36 PM George Edwards wrote: > Hi John, > > Thank you very much, it works! > > I appreciate your help very much! > > George > > On Wed, Mar 15, 2023, 11:05 AM John Sallay w

Re: How to force the decimation to schedule at least 16 output samples

2023-03-15 Thread George Edwards
Hi John, Thank you very much, it works! I appreciate your help very much! George On Wed, Mar 15, 2023, 11:05 AM John Sallay wrote: > The set_min_noutput_items function exists, but sadly it does nothing > (literally nothing). I've traced the value through the scheduler code to > verify this.

Re: How to force the decimation to schedule at least 16 output samples

2023-03-15 Thread John Sallay
The set_min_noutput_items function exists, but sadly it does nothing (literally nothing). I've traced the value through the scheduler code to verify this. The only way to mostly do what you want is through set_output_multiple (ie self.set_output_multiple(16). This will ensure that you always rec

Re: How to force the decimation to schedule at least 16 output samples

2023-03-15 Thread Jeff Long
The function is there. Perhaps you're not calling it correctly, but I can't tell. On Wed, Mar 15, 2023 at 11:11 AM George Edwards wrote: > Hi Jeff, > Thanks for the suggestion. > > I tried set_min_noutput_items(16) first in the __init__() method, then the > work() of Python file and each time I