On Thu, May 20, 2010 at 1:06 AM, ayuffa ayu...@gmail.com wrote:
Does anyone have another fix for this problem that DOES NOT produce HUGE
PDF/EPS files?
I believe that the latest SVN revision should allow you to set
rasterized=True for the call to contourf. I don't know if the relevant code
On 05/24/2010 04:55 AM, Benjamin Root wrote:
On Thu, May 20, 2010 at 1:06 AM, ayuffa ayu...@gmail.com
mailto:ayu...@gmail.com wrote:
Does anyone have another fix for this problem that DOES NOT produce HUGE
PDF/EPS files?
I believe that the latest SVN revision should allow you to
Yes, it's true that uncommenting path.simplify : False line inside the
matplotlibrc file fixes the artifacts. However, it also produces HUGE
PDF/EPS file sizes. Perhaps, it's better to change path.simplify parameter
as needed inside the code via:
import matplotlib.pyplot as plt
This is actually revealing a secondary bug. It is a bug that filled
objects are being simplified at all. For various reasons, the
simplification algorithm is not safe for use with filled regions (mainly
because it doesn't ensure the end points match up). The Agg backend
turns simplification
Jouni K. Sepp?nen wrote:
Jordan Dawe jd...@eos.ubc.ca writes:
Contourf plots that I output in vector format files have little
triangular glitches at the contour boundaries if the contoured array
is larger than about 200x200. The same files in png format are
perfect, even at very
Jouni K. Seppänen wrote:
Jordan Dawe jd...@eos.ubc.ca writes:
Contourf plots that I output in vector format files have little
triangular glitches at the contour boundaries if the contoured array
is larger than about 200x200. The same files in png format are
perfect, even at very high dpi