I wish I could say that it was because of a deep understanding of the inner
workings of matplotlib or a rock solid grasp of python 3's bytes vs strings,
but it wasn't. fig.savefig threw the TypeError: string argument expected,
got 'bytes' exception, so I figured BytesIO might work better with
Well, the methodology is sufficient and efficient, I'm OK with that :)
Thanks for these additional information.
Regards,
Le 2 nov. 2014 09:34, Scott Lasley slas...@space.umd.edu a écrit :
I wish I could say that it was because of a deep understanding of the
inner workings of matplotlib or a
On 1 November 2014 18:20, Hartmut Kaiser hartmut.kai...@gmail.com wrote:
Thanks Ian! Your detailed answer is much appreciated.
As you might have already guessed, we have quite some problems creating
clean geometries from the generated contour data. I have tried to put
together one
Would it make sense to at least emit a warning when a mask is encountered.
There are very few places in matplotlib where masked arrays are not allowed
(I think histograms is the other spot, but I can't remember for sure).
On Sun, Nov 2, 2014 at 11:10 AM, Ian Thomas ianthoma...@gmail.com wrote:
I just installed matplotlib 1.4.2 via pip, and executing the file
matplotlib-1.4.2/examples/pylab_examples/tex_demo.py from the source
tarball gives the same error:
Traceback (most recent call last):
File matplotlib-1.4.2/examples/pylab_examples/tex_demo.py, line 29,
in module
Ian,
You are using masked arrays where you shouldn't, again. The documentation
for tricontour states that it expects z to be an array, it doesn't say
masked array. If you pass it a masked array, it will ignore the
mask. Hence you have a number of triangles that include a vertex with a
