On Jun 25, 2008, at 8:38 PM, Michael Droettboom wrote: > Ahh -- 0.91 avoided this by using non-antialiased rendering by > default for pcolor as well as pcolormesh. That's probably what Rob > is seeing when he went from 0.91 to 0.98.
Indeed. Now that I think about it in the light of the discussion here, it may be that I have seen this behavior before, but not by default. What surprised me is that I was getting this sort of result using the same function as previously. A sample showing the different behavior might be something like: x, y = meshgrid(arange(50), arange(100)) y *= 1 + sin(x/30.0) y += 10.0*sqrt(x) z = (x+y)**2 figure() pcolor(x, y, z) figure() pcolor(x, y, z, antialiased=False) # pcolormesh gives similar results to antialiased=False # further tests with missing values in y y = np.ma.masked_where(y< 100, y) pcolor(x, y, z, antialiased=False) # pcolormesh fails. -Rob ---- Rob Hetland, Associate Professor Dept. of Oceanography, Texas A&M University http://pong.tamu.edu/~rob phone: 979-458-0096, fax: 979-845-6331 ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
