On 02/27/2014 02:06 AM, Michael Berman wrote:
> I have figured out what was happening for me. As I was deprecating the
> source code to put out publicly, I noticed something that looking at now
> was a glaring red flag. Inside my OOT, I was copying the GNURadio
> buffered data into a vector for c
I have figured out what was happening for me. As I was deprecating the
source code to put out publicly, I noticed something that looking at now
was a glaring red flag. Inside my OOT, I was copying the GNURadio buffered
data into a vector for computation on the large set of data. I knew that
it w
Martin,
Thank you for the quick response to my issue!
I cannot release the source code as is, however I can describe what I am
doing, and possibly if need be I can release a deprecated version that
still exhibits this behavior.
I am taking 1 MHz of spectrum and putting this through a 50 channel
On 02/26/2014 01:31 AM, Michael Berman wrote:
> I am seeing some odd behavior with an OOT decimation block. What I am
> seeing is chunks of data are being dropped down to noise for random
> calls of the work function in my OOT. To observe this happening, I
> tee'd off the connection going into my
I am seeing some odd behavior with an OOT decimation block. What I am
seeing is chunks of data are being dropped down to noise for random calls
of the work function in my OOT. To observe this happening, I tee'd off the
connection going into my OOT module and went strait into a file sink and
then
