On Sat, Jan 9, 2010 at 8:20 AM, Eric Emsellem wrote:
> Hi
> thanks A LOT for taking the time to test this and for the suggestions.
>
> Yes, pcolormesh is needed (or at least I think) because in the "real"
> example (the figures I am trying to make) the pixels are rotated meaning
> that these are p
Thinking about it: when matplotlib transfer the plot to ghostscript, is
there a parameter in the call for "gs" which limits the memory usage???
It seems that this is discussed in some posts about gs
Eric
On 09/01/10 04:25, Jae-Joon Lee wrote:
> I can reproduce this error with the current svn.
>
Hi
thanks A LOT for taking the time to test this and for the suggestions.
Yes, pcolormesh is needed (or at least I think) because in the "real"
example (the figures I am trying to make) the pixels are rotated meaning
that these are polygons which are not aligned with the axes. Imshow
cannot do tha
I can reproduce this error with the current svn.
I doubt if this is a matplotlib issue, because it works fine if the
number of axes is small.
To me, it seems as some memory error in the ghostscript, but my quick
googling did not show any relevant information.
So, I hope some postscript expert take
Hi
I finally managed to write a simplified version of my python script
which crashes when trying to save the figure as a postscript file. (this
is related to a previous post). See below. The script is provided, as
well as the full error message.
Sorry for the long script, but basically I am plott
