[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Effect of samples_per_symbol on benchmark_qt_loop

From: Ben Reynwar
Subject: Re: [Discuss-gnuradio] Effect of samples_per_symbol on benchmark_qt_loopback2.py
Date: Wed, 8 Dec 2010 07:10:30 -0700

I was using that many so I could see how it all worked better (plots
with two samples per symbol are a little less intuitive to look at).
I realize it's not of practical importance but I thought it was


On Tue, Dec 7, 2010 at 9:27 PM, Tom Rondeau <address@hidden> wrote:
> On Tue, Dec 7, 2010 at 12:42 AM, Ben Reynwar <address@hidden> wrote:
>> When I run 
>> gnuradio/gnuradio-examples/python/digital/benchmark_qt_loopback2.py
>> I get a strange dependence on samples_per_symbol.
>> I would naively have expected that the more samples per symbol the
>> better, however:
>> python benchmark_qt_loopback2.py --samples_per_symbol 10
>> produces no errors
>> whereas
>> python benchmark_qt_loopback2.py --samples_per_symbol 11
>> produces lots of errors
>> Does anyone have any idea what's going on here?
>> Cheers,
>> Ben
> That's a very large number of samples per symbol. I know I tested up
> to 10, but more than that's pretty excessive. Ok, more than 2 is
> excessive, really. Off the top of my head, I can't think of exactly
> what might be going wrong here, but you should really never need to
> use that many samples per symbol, anyway.
> Tom

reply via email to

[Prev in Thread] Current Thread [Next in Thread]