Re: [Discuss-gnuradio] Should return the number of input or the number of output?

2014-05-04 Thread Marcus Müller
Hi Activecat, it's a sink. As Martin said, keep it a sync block. Overriding forecast doesn't even make sense; why should the scheduler ask the block I'd like to have 2000 output items from you, how much input do you need if it's guaranteed to never produce output. Maybe I'm getting something

Re: [Discuss-gnuradio] Should return the number of input or the number of output?

2014-05-04 Thread Activecat
On Sun, May 4, 2014 at 4:39 PM, Marcus Müller marcus.muel...@ettus.comwrote: Hi Activecat, it's a sink. As Martin said, keep it a sync block. Overriding forecast doesn't even make sense; why should the scheduler ask the block I'd like to have 2000 output items from you, how much input do you

Re: [Discuss-gnuradio] Should return the number of input or the number of output?

2014-05-04 Thread Activecat
On Mon, May 5, 2014 at 3:45 AM, Marcus Müller marcus.muel...@ettus.comwrote: Hi Activecat, On 04.05.2014 12:32, Activecat wrote: This sink block needs to produce an 8-bit integer from every 9 elements it receives. Ok, this explains where the mutual confusion stems from: A sink block is

Re: [Discuss-gnuradio] Should return the number of input or the number of output?

2014-05-03 Thread Activecat
Part of this question has been partially discussed, as below. On Mon, Mar 10, 2014 at 9:18 PM, Martin Braun martin.br...@ettus.comwrote: OK, I admit I was unclear. Let's try from scratch: - The return function from work() or general_work() is the amount of items that were *produced*. Says,

Re: [Discuss-gnuradio] Should return the number of input or the number of output?

2014-03-11 Thread Marcus Müller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, it's basically the idea of not writing a special case for a single type of block; and if you are aware that sync blocks are only subclasses of normal blocks that implement a general_work which consumes *and* produces the return value of work,

Re: [Discuss-gnuradio] Should return the number of input or the number of output?

2014-03-11 Thread Activecat
Yes I agree with you all. Everything are now clear and readable. Thank you very much. Regards, Activecat On Tue, Mar 11, 2014 at 5:08 PM, Marcus Müller mar...@hostalia.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, it's basically the idea of not writing a special case for a

Re: [Discuss-gnuradio] Should return the number of input or the number of output?

2014-03-10 Thread Martin Braun
On 03/09/2014 04:58 AM, Activecat wrote: Dear Sir, A python sink block created by gr_modtool has below work() function, it returns the number of input items. def work(self, input_items, output_items): in0 = input_items[0] # +signal processing here+ return

Re: [Discuss-gnuradio] Should return the number of input or the number of output?

2014-03-10 Thread Activecat
On 03/09/2014 04:58 AM, Activecat wrote: Dear Sir, A python sink block created by gr_modtool has below work() function, it returns the number of input items. def work(self, input_items, output_items): in0 = input_items[0] # +signal processing here+

Re: [Discuss-gnuradio] Should return the number of input or the number of output?

2014-03-10 Thread Martin Braun
OK, I admit I was unclear. Let's try from scratch: - The return function from work() or general_work() is the amount of items that were *produced*. - In a sync block, the number of items produced is the number of items consumed, so we can use that to save the developer from manually consuming().

Re: [Discuss-gnuradio] Should return the number of input or the number of output?

2014-03-10 Thread Activecat
Dear Martin, Apparently the consistency of code across different source files is more emphasized than its clarity in individual file. Nevertheless that is clear now, thanks. Regards, Activecat On Mon, Mar 10, 2014 at 9:18 PM, Martin Braun martin.br...@ettus.comwrote: OK, I admit I was