Great, AB! Glad that works & you're welcome. Please do note that what
you're doing is technically not supported by GNU Radio even if it does
work, and the currently correct results may become incorrect (again) due
to any forthcoming changes in the GR scheduler. No matter how unlikely,
this scenario
Thank you for the quick response!
AB
From: Michael Dickens
Sent: Thursday, July 13, 2017 10:24:06 AM
To: Bakshi, Arjun; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Understanding produce, consume, and data streams
Hi AB - If I recall correctly, the o
Hi AB - If I recall correctly, the output stream is not cleared / zeroed in the
scheduler. So, it has, for all practical purposes, random data in it upon entry
to ::general_work (whether in C++ or Python). Also IIRC, a guarantee provided
by the scheduler is that there will be enough output data
Hi all,
Apologies for a possible duplicate message.
I've made a few OOT blocks and thought I had a handle on the process but I've
found something that I don't understand. I have a general block that "passes"
the input to the output stream. However, instead of doing something like:
out[:] = in0
