Shot in the dark here, but what if you set the rcParam "path.simplify" to False? There have been recent changes to that code.
Also, since the Agg backend doesn't have an associated GUI, you need to use the savefig() command and provide a filename, rather than using show(). Cheers, Mike Zane Selvans wrote: > Um, yeah. So my response got bounced because of the attachment. Take 2: > > For some reason my script bombed when I switched to the Agg backend, > trying to display to the screen (it said Figure has no method show()) > > So I output the plot as both a PDF and a PNG (still having backend: > agg in my rcfile) and in both of those cases, irregular gaps are > visible between the polygons making up the filled contours. This > wasn't the case with my previously installed setup. It looks as if > for some reason the vertices of the filled polygons are being > calculated differently from different sides of the same contour, > leading to overlap in some places, and gaps in others. You can download > the PDF version (in which the exact geometry is much clearer). > from: > > http://zaneselvans.org/dropbox/LinDensity_Grid.pdf > > Zane > > On Fri, Jun 12, 2009 at 5:51 AM, Michael Droettboom<md...@stsci.edu> wrote: > >> So you see this behavior if you switch to the Agg backend? That's the >> backend used to generate the images in the gallery. If there's a difference >> there, that would seem to suggest some tweaking of the macosx backend (which >> is still relatively new) is in order. >> >> Mike >> >> Zane Selvans wrote: >> >>> I just installed the latest SciPy Superpack in order to get access to >>> the scipy.spatial.KDTree class, and discovered that for some reason >>> now when I use contourf() lines get drawn at the boundaries between >>> the filled contours. Additionally, there is always a single vertical >>> line crossing from each contour boundary to the next. I'm guessing >>> that these are the edges of the filled polygons which are getting >>> drawn. This behavior doesn't seem to be consistent with the >>> contourf() documentation and when I run code in griddata_demo.py it >>> doesn't come out looking like the picture in the documentation/example >>> gallery... >>> >>> Is anyone else seeing this behavior? Is there a keyword I can use to >>> force the edges of the polygons not to get drawn? >>> >>> This is on Mac OS X 10.5.7, with >>> scipy.__version__ = 0.8.0.dev5635 >>> matplotlib.__version__ = 0.98.6svn >>> numpy.__version__=1.4.0.dev6728 >>> >>> As installed by superpack_2009.03.28.sh >>> from http://macinscience.org/?page_id=6 >>> >>> using: >>> backend: macosx >>> >>> Cheers, >>> Zane >>> >>> >>> >> -- >> Michael Droettboom >> Science Software Branch >> Operations and Engineering Division >> Space Telescope Science Institute >> Operated by AURA for NASA >> >> >> > > > > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
