Hi Mostafa, On 01.06.2014 19:23, Mostafa Alizadeh wrote: > This is not true because when I produce 1-3 packet of bits, the > scheduler doesn't go to the other blocks while there is items for > them! The scheduler calls the random bit generator for about 10 times!! I have tried that, and can disprove by example. My python code is under [1], feel free to test and modify. It generates timestamped output:
>21.341874 src: sleeping >22.342275 src: producing 3 items, 0 total so far >22.342600 src: sleeping >22.342774 sink: got 3 items, total 0 so far >23.343531 src: producing 3 items, 3 total so far >23.343843 src: sleeping >23.344011 sink: got 3 items, total 3 so far As you can see, the items that got produced are being processed *the same millisecond* the sources' work finishes. My source sleeps a second, then produces three items. Maybe there's a block downstream that needs bigger multiples of inputs than single bytes? Greetings, Marcus [1] https://github.com/marcusmueller/gr-trickling_items ; a GRC demo flowgraph is under examples/ _______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
