You're welcome, Anil; glad that was useful.
You can go either way with a block like the one you describe: general or sync. The block is sync when the correct parameters are set ("set_output_multiple(512);") or the like; and, really, the scheduler will handle the I/O correctly if you choose this block inheritance. If you choose to not use the GR features that provide the scheduler with hints of what to do, then going with a general block will give you more flexibility. There are internal (to the scheduler) trade-offs for either way, but both are workable options.
Cheers! - MLD
On Sun, Nov 19, 2017, at 01:00 PM, Anil Kumar Yerrapragada wrote:
Thank you very much for your response. This clears up things for me.One other question regarding this is: If the block takes in 4095 samples, returns 3854 onto its output is this still considered a sync (1:1) block or would it be a general block?I am leaning towards thinking that any block that does not return the same number of samples as it took in in each call of work would be a general block since the ratio of input to output is not 1:1.
No comments:
Post a Comment