On 10/12/2010 05:14 PM, Eric Blossom wrote: > Yes, I've seen this. > > Eric > > > Any speculation about why this is?
If you look at the code, it uses numpy.maximum(a,b) to compute the max function over the vector. But unless numpy.maximum() is implemented in a completely-stupid way, I can't see it being "computey" enough to cause this issue. I noticed that if I lowered the update rate to 2, it started working again. Three was no good, as was four. Five, was right out. Maybe an OpenGL weirdness on that particular platform, since my other machine, which only has about 50% more "go" than the Atom D-510 doesn't have this problem, even for the same GnuRadio versions. -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
