matplotlib-devel Mailing List for matplotlib (Page 5)

Thanks.  I have increased the tolerance in the SVN repository in r 
8926/r8927.

Cheers,
Mike

On 01/18/2011 01:29 PM, Sandro Tosi wrote:
> Hi,
>
> On Tue, Jan 18, 2011 at 15:00, Michael Droettboom<md...@st...>  wrote:
>> I'm not sure PIL enters into it -- there shouldn't be any code path
>> involving PIL in that case.
>>
>> I think this a case where the image comparison tolerance needs to be
>> increased.  You would do this be passing a "tol" parameter to the
>> image_comparison decorator on the pcolormesh test.  The default is 1e-3,
>> but it should be conservatively increased until the test passes.  You
>> can perform this experiment yourself, or attach the result image for the
>> test to this list and I can experiment to find a correct value.
> I'm attaching the images, just for reference; as you can see, the
> difference is very tiny and with a tolerance of 0.02 I was able to
> pass the test (RMS Value: 0.0116511801977).
>
> Cheers,

Hi,

On Tue, Jan 18, 2011 at 15:00, Michael Droettboom <md...@st...> wrote:
> I'm not sure PIL enters into it -- there shouldn't be any code path
> involving PIL in that case.
>
> I think this a case where the image comparison tolerance needs to be
> increased.  You would do this be passing a "tol" parameter to the
> image_comparison decorator on the pcolormesh test.  The default is 1e-3,
> but it should be conservatively increased until the test passes.  You
> can perform this experiment yourself, or attach the result image for the
> test to this list and I can experiment to find a correct value.

I'm attaching the images, just for reference; as you can see, the
difference is very tiny and with a tolerance of 0.02 I was able to
pass the test (RMS Value: 0.0116511801977).

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

I'm not sure PIL enters into it -- there shouldn't be any code path 
involving PIL in that case.

I think this a case where the image comparison tolerance needs to be 
increased.  You would do this be passing a "tol" parameter to the 
image_comparison decorator on the pcolormesh test.  The default is 1e-3, 
but it should be conservatively increased until the test passes.  You 
can perform this experiment yourself, or attach the result image for the 
test to this list and I can experiment to find a correct value.

Mike

On 01/17/2011 02:44 PM, Sandro Tosi wrote:
> Hi Ben,
> thanks for the fast reply!
>
> On Mon, Jan 17, 2011 at 20:35, Benjamin Root<ben...@ou...>  wrote:
>> I have seen this before, and I think it was discussed once before.
>> Visually, there is very little difference,
> indeed, looking at the 2 images, I can't see any difference.
>
>> but supposedly there is some sort
>> of issue with different PIL versions.  What version of PIL do you have?
> 1.1.7
>
> Cheers,

Dear matplotlib developpers,

I use matplotlib for several years and I'm very satisfied with the it.
I started using the basemap package a few days ago, and I noticed something
that looks like a bug :

With the Mollweide projection (and others too), when specifying rsphere=1.0,
the coastlines is not drawn in the
left part of the plot. With rsphere=2.0 the hidden part is smaller, and with
rsphere=10.0 it is not visible.

I'm using matplotlib 1.0.0 and basemap 1.0
To reproduce the bug :

m = Basemap(projection='moll',lon_0=180,rsphere=1.0)
m.drawcoastlines(linewidth=0.5, color='grey')     # draw discrete coastlines
m.drawmapboundary()        # draw a line around the map region
show()

Finally the hammer projection is missing for me :

In [5]: m=Basemap(projection='hammer',lon_0=180)
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)

/home/nat/pkg/python-matplotlib-basemap/<ipython console> in <module>()

/usr/lib/python2.7/site-packages/mpl_toolkits/basemap/__init__.pyc in
__init__(self, llcrnrlon, llcrnrlat, urcrnrlon, urcrnrlat, llcrnrx, llcrnry,
urcrnrx, urcrnry, width, height, projection, resolution, area_thresh,
rsphere, lat_ts, lat_1, lat_2, lat_0, lon_0, lon_1, lon_2, no_rot,
suppress_ticks, satellite_height, boundinglat, fix_aspect, anchor, ax)
    698                 print 'warning: width and height keywords ignored
for %s projection' % _projnames[self.projection]
    699         else:
--> 700             raise ValueError(_unsupported_projection % projection)
    701
    702         # initialize proj4


ValueError: 'hammer' is an unsupported projection.
The supported projections are:
 aeqd             Azimuthal Equidistant
 poly             Polyconic
 gnom             Gnomonic
 moll             Mollweide
 tmerc            Transverse Mercator
 nplaea           North-Polar Lambert Azimuthal
 gall             Gall Stereographic Cylindrical
 mill             Miller Cylindrical
 merc             Mercator
 stere            Stereographic
 npstere          North-Polar Stereographic
 geos             Geostationary
 nsper            Near-Sided Perspective
 vandg            van der Grinten
 laea             Lambert Azimuthal Equal Area
 mbtfpq           McBryde-Thomas Flat-Polar Quartic
 sinu             Sinusoidal
 spstere          South-Polar Stereographic
 lcc              Lambert Conformal
 npaeqd           North-Polar Azimuthal Equidistant
 eqdc             Equidistant Conic
 cyl              Cylindrical Equidistant
 omerc            Oblique Mercator
 aea              Albers Equal Area
 spaeqd           South-Polar Azimuthal Equidistant
 ortho            Orthographic
 cass             Cassini-Soldner
 splaea           South-Polar Lambert Azimuthal
 robin            Robinson

Seems to resolve the problem!
Thanks

2011/1/18 Jae-Joon Lee <lee...@gm...>:
> Can you see if setting the "should_simplify" to False work? i.e.,
>
> path=cs.collections[5].get_paths()[0] #210 vertices
> path.should_simplify = False
> path.to_polygons()
>
> At least, it seems to conserve the number of vertices.
>
> Regards,
>
> -JJ
>
>
> On Tue, Jan 18, 2011 at 5:07 PM, Lionel Roubeyrie
> <lio...@gm...> wrote:
>> Hi,
>> is there a existing patch for this problem or do we have to use/modify
>> iter_segments for the moment?
>> thanks
>>
>> 2011/1/15 Lionel Roubeyrie <lio...@gm...>:
>>> The problem appends on some paths/polygons, not all. Have a look at
>>> the joined pictures. The to_polygons method normally take care about
>>> polygons holes, but here some vertices are not converted, resulting in
>>> wrong geometries.
>>> #############
>>> import numpy as np
>>> import pylab as plb
>>> a=np.recfromtxt('rpatch3.grid', delimiter='\t',names=True)
>>> lev=np.linspace(a.ux.min(), a.ux.max(), 10)
>>> cs=plb.tricontourf(a.lon, a.lat, a.ux, lev)
>>> path=cs.collections[5].get_paths()[0] #210 vertices
>>> path.to_polygons() #16 vertices :(
>>> #############
>>> Cheers
>>>
>>> 2011/1/14 Michael Droettboom <md...@st...>:
>>>> It's not obvious to me that this is wrong.  The path has a MOVETO
>>>> command (1) in the middle, and thus should require the creation of two
>>>> polygons.  Can you provide some code or pictures that demonstrate the
>>>> problem?
>>>>
>>>> Mike
>>>>
>>>> On 01/13/2011 05:54 PM, Lionel Roubeyrie wrote:
>>>>> Hi all,
>>>>> Using the last 1.0.1 matplotlib version,sometimes exporting paths to
>>>>> polygons gives wrong results like here (paths come from a
>>>>> tricontourset) :
>>>>> In [94]: path
>>>>> Out[94]:
>>>>> Path([[ 172.0079229   -43.79390934]
>>>>>   [ 171.97660793  -43.785     ]
>>>>>   [ 171.96206864  -43.78273625]
>>>>>   [ 171.959       -43.78114859]
>>>>>   ...
>>>>>   [ 171.593       -44.00678244]
>>>>>   [ 171.64906502  -44.01      ]
>>>>>   [ 171.654       -44.01077106]
>>>>>   [ 171.7068607   -44.0160044 ]], [1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>>> 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1 2 2 2 2 2 2 2 2 2
>>>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2])
>>>>> In [95]: path.vertices.shape
>>>>> Out[95]: (210, 2)
>>>>>
>>>>> but to_polygons gives another result :
>>>>> In [98]: path.to_polygons()
>>>>> Out[98]:
>>>>> [array([[ 172.0079229 ,  -43.79390934],
>>>>>         [ 171.86039224,  -43.65      ],
>>>>>         [ 172.081     ,  -43.54450289],
>>>>>         [ 172.386     ,  -43.57010293],
>>>>>         [ 172.60631978,  -43.67753099],
>>>>>         [ 172.59231502,  -43.71219961],
>>>>>         [ 172.325     ,  -43.78095532],
>>>>>         [ 172.02      ,  -43.79497729]]),
>>>>>   array([[ 171.715     ,  -44.0160044 ],
>>>>>         [ 173.02676111,  -43.92      ],
>>>>>         [ 172.935     ,  -43.53340591],
>>>>>         [ 171.40281884,  -43.70029758],
>>>>>         [ 171.37760645,  -43.94389688],
>>>>>         [ 171.54044973,  -44.0037666 ],
>>>>>         [ 171.7068607 ,  -44.0160044 ],
>>>>>         [ 171.7068607 ,  -44.0160044 ]])]
>>>>>
>>>>> Cheers
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Michael Droettboom
>>>> Science Software Branch
>>>> Space Telescope Science Institute
>>>> Baltimore, Maryland, USA
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Protect Your Site and Customers from Malware Attacks
>>>> Learn about various malware tactics and how to avoid them. Understand
>>>> malware threats, the impact they can have on your business, and how you
>>>> can protect your company and customers by using code signing.
>>>> http://p.sf.net/sfu/oracle-sfdevnl
>>>> _______________________________________________
>>>> Matplotlib-devel mailing list
>>>> Mat...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>>
>>>
>>>
>>>
>>> --
>>> Lionel Roubeyrie
>>> lio...@gm...
>>> http://youarealegend.blogspot.com
>>>
>>
>>
>>
>> --
>> Lionel Roubeyrie
>> lio...@gm...
>> http://youarealegend.blogspot.com
>>
>> ------------------------------------------------------------------------------
>> Protect Your Site and Customers from Malware Attacks
>> Learn about various malware tactics and how to avoid them. Understand
>> malware threats, the impact they can have on your business, and how you
>> can protect your company and customers by using code signing.
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>



-- 
Lionel Roubeyrie
lio...@gm...
http://youarealegend.blogspot.com

Can you see if setting the "should_simplify" to False work? i.e.,

path=cs.collections[5].get_paths()[0] #210 vertices
path.should_simplify = False
path.to_polygons()

At least, it seems to conserve the number of vertices.

Regards,

-JJ


On Tue, Jan 18, 2011 at 5:07 PM, Lionel Roubeyrie
<lio...@gm...> wrote:
> Hi,
> is there a existing patch for this problem or do we have to use/modify
> iter_segments for the moment?
> thanks
>
> 2011/1/15 Lionel Roubeyrie <lio...@gm...>:
>> The problem appends on some paths/polygons, not all. Have a look at
>> the joined pictures. The to_polygons method normally take care about
>> polygons holes, but here some vertices are not converted, resulting in
>> wrong geometries.
>> #############
>> import numpy as np
>> import pylab as plb
>> a=np.recfromtxt('rpatch3.grid', delimiter='\t',names=True)
>> lev=np.linspace(a.ux.min(), a.ux.max(), 10)
>> cs=plb.tricontourf(a.lon, a.lat, a.ux, lev)
>> path=cs.collections[5].get_paths()[0] #210 vertices
>> path.to_polygons() #16 vertices :(
>> #############
>> Cheers
>>
>> 2011/1/14 Michael Droettboom <md...@st...>:
>>> It's not obvious to me that this is wrong.  The path has a MOVETO
>>> command (1) in the middle, and thus should require the creation of two
>>> polygons.  Can you provide some code or pictures that demonstrate the
>>> problem?
>>>
>>> Mike
>>>
>>> On 01/13/2011 05:54 PM, Lionel Roubeyrie wrote:
>>>> Hi all,
>>>> Using the last 1.0.1 matplotlib version,sometimes exporting paths to
>>>> polygons gives wrong results like here (paths come from a
>>>> tricontourset) :
>>>> In [94]: path
>>>> Out[94]:
>>>> Path([[ 172.0079229   -43.79390934]
>>>>   [ 171.97660793  -43.785     ]
>>>>   [ 171.96206864  -43.78273625]
>>>>   [ 171.959       -43.78114859]
>>>>   ...
>>>>   [ 171.593       -44.00678244]
>>>>   [ 171.64906502  -44.01      ]
>>>>   [ 171.654       -44.01077106]
>>>>   [ 171.7068607   -44.0160044 ]], [1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>> 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1 2 2 2 2 2 2 2 2 2
>>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2])
>>>> In [95]: path.vertices.shape
>>>> Out[95]: (210, 2)
>>>>
>>>> but to_polygons gives another result :
>>>> In [98]: path.to_polygons()
>>>> Out[98]:
>>>> [array([[ 172.0079229 ,  -43.79390934],
>>>>         [ 171.86039224,  -43.65      ],
>>>>         [ 172.081     ,  -43.54450289],
>>>>         [ 172.386     ,  -43.57010293],
>>>>         [ 172.60631978,  -43.67753099],
>>>>         [ 172.59231502,  -43.71219961],
>>>>         [ 172.325     ,  -43.78095532],
>>>>         [ 172.02      ,  -43.79497729]]),
>>>>   array([[ 171.715     ,  -44.0160044 ],
>>>>         [ 173.02676111,  -43.92      ],
>>>>         [ 172.935     ,  -43.53340591],
>>>>         [ 171.40281884,  -43.70029758],
>>>>         [ 171.37760645,  -43.94389688],
>>>>         [ 171.54044973,  -44.0037666 ],
>>>>         [ 171.7068607 ,  -44.0160044 ],
>>>>         [ 171.7068607 ,  -44.0160044 ]])]
>>>>
>>>> Cheers
>>>>
>>>>
>>>
>>>
>>> --
>>> Michael Droettboom
>>> Science Software Branch
>>> Space Telescope Science Institute
>>> Baltimore, Maryland, USA
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Protect Your Site and Customers from Malware Attacks
>>> Learn about various malware tactics and how to avoid them. Understand
>>> malware threats, the impact they can have on your business, and how you
>>> can protect your company and customers by using code signing.
>>> http://p.sf.net/sfu/oracle-sfdevnl
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>
>>
>>
>> --
>> Lionel Roubeyrie
>> lio...@gm...
>> http://youarealegend.blogspot.com
>>
>
>
>
> --
> Lionel Roubeyrie
> lio...@gm...
> http://youarealegend.blogspot.com
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Hi,
is there a existing patch for this problem or do we have to use/modify
iter_segments for the moment?
thanks

2011/1/15 Lionel Roubeyrie <lio...@gm...>:
> The problem appends on some paths/polygons, not all. Have a look at
> the joined pictures. The to_polygons method normally take care about
> polygons holes, but here some vertices are not converted, resulting in
> wrong geometries.
> #############
> import numpy as np
> import pylab as plb
> a=np.recfromtxt('rpatch3.grid', delimiter='\t',names=True)
> lev=np.linspace(a.ux.min(), a.ux.max(), 10)
> cs=plb.tricontourf(a.lon, a.lat, a.ux, lev)
> path=cs.collections[5].get_paths()[0] #210 vertices
> path.to_polygons() #16 vertices :(
> #############
> Cheers
>
> 2011/1/14 Michael Droettboom <md...@st...>:
>> It's not obvious to me that this is wrong.  The path has a MOVETO
>> command (1) in the middle, and thus should require the creation of two
>> polygons.  Can you provide some code or pictures that demonstrate the
>> problem?
>>
>> Mike
>>
>> On 01/13/2011 05:54 PM, Lionel Roubeyrie wrote:
>>> Hi all,
>>> Using the last 1.0.1 matplotlib version,sometimes exporting paths to
>>> polygons gives wrong results like here (paths come from a
>>> tricontourset) :
>>> In [94]: path
>>> Out[94]:
>>> Path([[ 172.0079229   -43.79390934]
>>>   [ 171.97660793  -43.785     ]
>>>   [ 171.96206864  -43.78273625]
>>>   [ 171.959       -43.78114859]
>>>   ...
>>>   [ 171.593       -44.00678244]
>>>   [ 171.64906502  -44.01      ]
>>>   [ 171.654       -44.01077106]
>>>   [ 171.7068607   -44.0160044 ]], [1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>> 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1 2 2 2 2 2 2 2 2 2
>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2])
>>> In [95]: path.vertices.shape
>>> Out[95]: (210, 2)
>>>
>>> but to_polygons gives another result :
>>> In [98]: path.to_polygons()
>>> Out[98]:
>>> [array([[ 172.0079229 ,  -43.79390934],
>>>         [ 171.86039224,  -43.65      ],
>>>         [ 172.081     ,  -43.54450289],
>>>         [ 172.386     ,  -43.57010293],
>>>         [ 172.60631978,  -43.67753099],
>>>         [ 172.59231502,  -43.71219961],
>>>         [ 172.325     ,  -43.78095532],
>>>         [ 172.02      ,  -43.79497729]]),
>>>   array([[ 171.715     ,  -44.0160044 ],
>>>         [ 173.02676111,  -43.92      ],
>>>         [ 172.935     ,  -43.53340591],
>>>         [ 171.40281884,  -43.70029758],
>>>         [ 171.37760645,  -43.94389688],
>>>         [ 171.54044973,  -44.0037666 ],
>>>         [ 171.7068607 ,  -44.0160044 ],
>>>         [ 171.7068607 ,  -44.0160044 ]])]
>>>
>>> Cheers
>>>
>>>
>>
>>
>> --
>> Michael Droettboom
>> Science Software Branch
>> Space Telescope Science Institute
>> Baltimore, Maryland, USA
>>
>>
>> ------------------------------------------------------------------------------
>> Protect Your Site and Customers from Malware Attacks
>> Learn about various malware tactics and how to avoid them. Understand
>> malware threats, the impact they can have on your business, and how you
>> can protect your company and customers by using code signing.
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>
>
>
> --
> Lionel Roubeyrie
> lio...@gm...
> http://youarealegend.blogspot.com
>



-- 
Lionel Roubeyrie
lio...@gm...
http://youarealegend.blogspot.com

Hey,

The test_rendered.html file probably should have been removed from the
release version. The idea behind this was to compare a PNG of the
browser rendered HTML5 plot with the standard PNG backend. (So users
without HTML5 support could see how the plugin performed).

These rendered PNG's are generated from the main test.html page by
running the rec.py receiver, and using the 'Connect' and 'Put images
to server' buttons on the bottom of test.html

Unfortunately the connect method uses a hardcoded IP address for the
WebSocket and so will need to be changed if you wanted to get this
working.

In short, as long as test.html produces three columns of plots (HTML5,
PNG and SVG), things are working fine.

I apologise for the slipshod release that left this code in :)

Cheers,

Simon Ratcliffe

On Fri, Jan 14, 2011 at 11:02 AM, Akad Demo <aka...@gm...> wrote:
> Hello,
>
> I run the test.py example from the folder mplh5canvas/test. This example
> generated in the output folder 2 html pages (test.html and
> test_rendered.html) and also 2 images (filename.png and filename.svg). The
> test.html page is displayed ok, but when I open the test_rendered.html page
> the images from the column "H5 Canvas (PNG from Chrome 4.0 OSX)" are not
> displayed.
>
> After I studied the source code of the test.py example I saw the following
> line:
>
> (line 85)  thtml += "<td><img src='%s' width='%dpx' height='%dpx' />" %
> ("h5canvas_" + png_filename, w, h)
>
> Now the question is: What is supposed to be "h5canvas_" + png_filename?
> There is no image generated with this name in the output folder.
>
> The HTML 5 Canvas Backend was downloaded from here:
> http://code.google.com/p/mplh5canvas/downloads/list
>
> Thanks!
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Dear Matplotlib developers,

Attached is a patch to improve the functionality of legend.
The two biggest changes are as follows,

* Drawing of legend is delegated to "legend handlers".
* Introduces a new "Container" class. This is primarily to support
legend of complex plots (e.g., bar, errorbar, etc).

The first change is to ease the creation of customized legends. See
"legend_demo_custom_handler.py" for example.
The second change is to support legend of complex plots. Axes
instances now have a "containers" attribute. And this is only intended
to be used for generating a legend. For example, "bar" plots create a
series of Rectangle patches. Previously, it returned a list of these
patches. With the current change, it creates a container object of
these rectangle patches and return it instead. As the container class
is derived from a tuple, it should be backward-compatible.
Furthermore, the container object is added to the Axes.containers
attributes. And legend command use this "container" attribute to
properly create a legend for the bar.

A two example figures are attached.

As this patch introduces relatively significant changes. I wanted to
get some comments from others before I commit.
The change will be divided into four commits.

Regards,

-JJ

Hi,
I noticed several tracebacks during doc building, so I'm adding them
here so we can get them fixed; let's start:

reading sources... [ 54%] examples/pylab_examples/geo_demo
/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/sphinxext/plot_directive.p
y:322: PlotWarning: Exception running plot
/home/morph/deb/build-area/matplotlib-1.0.1-test/doc/mpl_examples/pyla
b_examples/geo_demo.py
Traceback (most recent call last):
  File "/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/sphinxext/plot_directive.py",
line 319, in render_figures
    run_code(plot_path, function_name, plot_code, context=context)
  File "/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/sphinxext/plot_directive.py",
line 230, in run_code
    "__plot__", fd, fname, ('py', 'r', imp.PY_SOURCE))
  File "geo_demo.py", line 10, in <module>
  File "/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/pyplot.py",
line 658, in subplot
    a = fig.add_subplot(*args, **kwargs)
  File "/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/figure.py",
line 687, in add_subplot
    a = subplot_class_factory(projection_class)(self, *args, **kwargs)
  File "/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/axes.py",
line 8380, in __init__
    self._axes_class.__init__(self, fig, self.figbox, **kwargs)
  File "custom_projection_example.py", line 33, in __init__
TypeError: expected string or Unicode object, NoneType found

  warnings.warn(s, PlotWarning)

---

reading sources... [ 57%] examples/pylab_examples/image_demo2
/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/sphinxext/plot_directive.py:322:
PlotWarning: Exception running plot
/home/morph/deb/build-area/matplotlib-1.0.1-test/doc/mpl_examples/pylab_examples/image_demo2.py
Traceback (most recent call last):
  File "/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/sphinxext/plot_directive.py",
line 319, in render_figures
    run_code(plot_path, function_name, plot_code, context=context)
  File "/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/sphinxext/plot_directive.py",
line 230, in run_code
    "__plot__", fd, fname, ('py', 'r', imp.PY_SOURCE))
  File "image_demo2.py", line 9, in <module>
IOError: [Errno 2] No such file or directory:
'/home/morph/deb/build-area/matplotlib-1.0.1-test/sampledata/ct.raw'

  warnings.warn(s, PlotWarning)

(see other email about missing ct.raw in sampledata tarball)

---

reading sources... [ 61%] examples/pylab_examples/loadrec
/usr/lib/pymodules/python2.6/xlwt/Cell.py:17: DeprecationWarning:
struct integer overflow masking is deprecated
  return pack('<5HL', 0x00FD, 10, self.rowx, self.colx, self.xf_idx,
self.sst_idx)
/usr/lib/pymodules/python2.6/xlwt/Cell.py:225: DeprecationWarning:
struct integer overflow masking is deprecated
  pieces.append(pack('<4H', 0x00BD, 6 * nc + 6, rowx, icolx))
/usr/lib/pymodules/python2.6/xlwt/Cell.py:227: DeprecationWarning:
struct integer overflow masking is deprecated
  pieces.append(pack('<H', lastcolx))

---

reading sources... [ 81%] examples/units/artist_tests
/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/sphinxext/plot_directive.p
y:322: PlotWarning: Exception running plot
/home/morph/deb/build-area/matplotlib-1.0.1-test/doc/mpl_examples/unit
s/artist_tests.py
Traceback (most recent call last):
  File "/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/sphinxext/plot_directive.py",
line 319, in render_figures
    run_code(plot_path, function_name, plot_code, context=context)
  File "/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/sphinxext/plot_directive.py",
line 230, in run_code
    "__plot__", fd, fname, ('py', 'r', imp.PY_SOURCE))
  File "artist_tests.py", line 30, in <module>
  File "/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/collections.py",
line 836, in __init__
    self.set_segments(segments)
  File "/home/morph/deb/build-area/matplotlib-1.0.1-test/build/lib.linux-x86_64-2.6/matplotlib/collections.py",
line 845, in set_segments
    seg = np.asarray(seg, np.float_)
  File "/usr/lib/pymodules/python2.6/numpy/core/numeric.py", line 261,
in asarray
    return array(a, dtype, copy=False, order=order)
ValueError: setting an array element with a sequence.

  warnings.warn(s, PlotWarning)

---

Severals:

* (WARNING/2) Block quote ends without a blank line; unexpected unindent.
* (ERROR/3) Unexpected indentation.
* (WARNING/2) malformed hyperlink target.
* WARNING: document isn't included in any toctree
* WARNING: unusable reference target found

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Hi,

I noticed some erroneous behaviour when using a
LinearSegmentedColormap with an "under" color and different numbers of
color levels. The attached script replicates the behaviour, whereby
lowering the number of colors causes less of the values to be
considered "under" the vmin. I tracked the problem back to the
Colormap class where the results of Normalize are multiplied by the
number of color levels (N) and casted as an int to be used as indices
in the color array. The expected behaviour would be that all negative
values should be considered "under", however the results of the cast
means that anything between 0 and -0.5 will be set to 0 and therefore
will be in the normal color range for the colormap. The attached patch
overcomes this by setting all negative values to -1 before applying
the cast.

Thanks for your help,
Eoghan

Hi,

On Tue, Jan 4, 2011 at 19:11, Jakub Wilk <jw...@de...> wrote:
> Package: python-matplotlib-doc
> Version: 0.99.3-1
> Severity: minor
>
> There are several "Exception occurred rendering plot" warnings in the
> generated documentation:
>
> $ cd /usr/share/doc/python-matplotlib-doc/html/ && grep -r 'Exception
> occurred' .
> ./users/screenshots.html:[<a class="reference external"
> href="../plot_directive/mpl_examples/pylab_examples/scatter_demo2.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./users/screenshots.html:[<a class="reference external"
> href="../plot_directive/mpl_examples/api/date_demo.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./users/screenshots.html:[<a class="reference external"
> href="../plot_directive/mpl_examples/pylab_examples/finance_work2.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./users/screenshots.html:[<a class="reference external"
> href="../plot_directive/pyplots/plotmap.py">source code</a>]<p>Exception
> occurred rendering plot.</p>
> ./examples/units/date_support.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/units/date_support.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/units/basic_units.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/units/basic_units.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/units/artist_tests.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/units/artist_tests.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/axes_grid/demo_image.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/axes_grid/demo_image.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/pylab_examples/data_helper.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/pylab_examples/data_helper.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/pylab_examples/date_demo2.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/pylab_examples/date_demo2.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/pylab_examples/geo_demo.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/pylab_examples/geo_demo.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/pylab_examples/centered_ticklabels.html:[<a class="reference
> external"
> href="../../plot_directive/mpl_examples/pylab_examples/centered_ticklabels.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/pylab_examples/finance_demo.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/pylab_examples/finance_demo.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/pylab_examples/date_demo1.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/pylab_examples/date_demo1.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/pylab_examples/finance_work2.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/pylab_examples/finance_work2.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/pylab_examples/loadrec.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/pylab_examples/loadrec.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/pylab_examples/scatter_demo2.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/pylab_examples/scatter_demo2.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/pylab_examples/multipage_pdf.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/pylab_examples/multipage_pdf.py">source
> code</a>]<p>Exception occurred rendering plot.</p>
> ./examples/api/date_demo.html:[<a class="reference external"
> href="../../plot_directive/mpl_examples/api/date_demo.py">source
> code</a>]<p>Exception occurred rendering plot.</p>

The updated list is:

api/axes_api.html
api/pyplot_api.html
examples/api/hinton_demo.html
examples/api/radar_chart.html
examples/api/sankey_demo.html
examples/pylab_examples/anchored_artists.html
examples/pylab_examples/arrow_demo.html
examples/pylab_examples/axes_zoom_effect.html
examples/pylab_examples/data_helper.html
examples/pylab_examples/demo_bboximage.html
examples/pylab_examples/geo_demo.html
examples/pylab_examples/image_demo2.html
examples/pylab_examples/legend_auto.html
examples/pylab_examples/multipage_pdf.html
examples/units/artist_tests.html
examples/units/basic_units.html
users/annotations_guide.html
users/screenshots.html

But I have some problems debugging these issues, since when I run the
code by-hand, it works fine but in the html file it's not shown. How
can I debug that? in the log there's nothing about these problems (but
other error, I'll follow them up in another mail).

Thanks in advance,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Message for matplotlib developers

I have posted a message on the matplotlib-users list, but it may be of interest to some in the -devel list as well. Here is an excerpt describing an installation problem, and workaround, that affects Mac OS X and matplotlib.

I am new to Python, and have tried installing matplotlib on a Mac OS X 10.6 (Snow Leopard). In spite of excellent tools and documentation provided, the installation was unsuccessful:
- my computer is 10.6.6 (fully updated Snow Leopard)
- with full Xcode (c developers) code installed
- it reports Python 2.6.1 installed
- it installs packages such as numpy and biopython ok (which gives me a little confidence that I am doing things correctly)

But when I tried to install matplotlib 1.0.1, I encountered the following problems:
- the matplotlib mkpg .dmg files will not run as they advise Python 2.6 is required (but which is already installed!)
- upgrading to Python 2.7 did not fix this problem and the error message continued
- using tar and then installing via Python install files resulted in an unsatisfied compiler reference from "lipo"
- installing Python easy-install and using .egg scripts produced the same error message

A call for help on the matplotlib-users list produced a suggestion to go back to matplotlib 1.0.0 (not 1.0.1). This worked on one Mac, but did not work on a second Mac (with what I thought was identical configuration).
Finally, a general solution was found using MacPorts, as follows:

> **update** matplotlib 1.0.0 setup worked on one but did not work on a second Mac OS X 10.6.6. The second one again failed with a missing dependency. It seems to depend on what previous packages may have been installed.
> The following seems to be a complete fix:
> 1. On Mac OS X 10.6.x (in my case...6)
> 2. Install Apple Xcode (requires registration as an Apple developer)
> 3. Install MacPorts http://www.macports.org/
> 4. Check that all library dependencies for matplotlib in Python 2.6 have been satisfied by first running (with Administrator privileges):
> 	sudo port install py26-matplotlib
> (this will use MacPorts script to install matplotlib 1.0.0)
> 5. (optional) you can reinstall now matplotlib from http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.0/matplotlib-1.0.0.tar.gz/download
> **now** it works :-)

The above may suggest that matplotlib may have a dependency that is not present on a virgin OSX Xcode machine but which is incidentally installed by some other package usually present on a developer's machine and so whose absence is not noticed when preparing the installation script.

I hope the above report is of assistance to the devel community. I am a newbie to this so won't be of much help to you other than having found and documented the problem.

Many thanks for bringing matplotlib to the world!

Leslie Burnett
Sydney University

Hi Ben,
thanks for the fast reply!

On Mon, Jan 17, 2011 at 20:35, Benjamin Root <ben...@ou...> wrote:
> I have seen this before, and I think it was discussed once before.
> Visually, there is very little difference,

indeed, looking at the 2 images, I can't see any difference.

> but supposedly there is some sort
> of issue with different PIL versions.  What version of PIL do you have?

1.1.7

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

On Mon, Jan 17, 2011 at 1:28 PM, Sandro Tosi <mo...@de...> wrote:

> Hi,
> I was playing with test suite and I noticed that :
>
> morph@zion:~/deb/build-area/matplotlib-1.0.1$
> PYTHONPATH=build/lib.linux-x86_64-2.6 python -c "import matplotlib as
> m ; m.test(verbosity=1)"
> /usr/lib/pymodules/python2.6/nose/plugins/manager.py:391: UserWarning:
> Module matplotlib was already imported from
>
> /home/morph/deb/build-area/matplotlib-1.0.1/build/lib.linux-x86_64-2.6/matplotlib/__init__.pyc,
> but /usr/lib/pymodules/python2.6 is being added to sys.path
>  import pkg_resources
>
> ..K........K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..KE.K..K..K..K..K..K/home/morph/deb/build-area/matplotlib-1.0.1/build/lib.linux-x86_64-2.6/matplotlib/axes.py:2381:
> UserWarning: Attempting to set identical left==right results
> in singular transformations; automatically expanding.
> left=730139.0, right=730139.0
>  + 'left=%s, right=%s') % (left, right))
> ...K..KK..K..K.....K..K..K..K..K....K..K..K....K..K..K..K..K
> ======================================================================
> ERROR: matplotlib.tests.test_axes.test_pcolormesh
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>  File "/usr/lib/pymodules/python2.6/nose/case.py", line 183, in runTest
>    self.test(*self.arg)
>  File
> "/home/morph/deb/build-area/matplotlib-1.0.1/build/lib.linux-x86_64-2.6/matplotlib/testing/decorators.py",
> line 32, in failer
>    result = f(*args, **kwargs)
>  File
> "/home/morph/deb/build-area/matplotlib-1.0.1/build/lib.linux-x86_64-2.6/matplotlib/testing/decorators.py",
> line 126, in decorated_compare_images
>    '(RMS %(rms).3f)'%err)
> ImageComparisonFailure: images not close:
>
> /home/morph/deb/build-area/matplotlib-1.0.1/result_images/test_axes/pcolormesh.png
> vs.
> /home/morph/deb/build-area/matplotlib-1.0.1/result_images/test_axes/expected-pcolormesh.png
> (RMS 116.512)
>
> ----------------------------------------------------------------------
> Ran 150 tests in 107.607s
>
> FAILED (KNOWNFAIL=46, errors=1)
>
> Except for the UserWarning, there is an error in the suite: is someone
> else able to replicate it? is it another KNOWNFAIL?
>
> Cheers,
> --
> Sandro Tosi (aka morph, morpheus, matrixhasu)
> My website: http://matrixhasu.altervista.org/
> Me at Debian: http://wiki.debian.org/SandroTosi
>
>
I have seen this before, and I think it was discussed once before.
Visually, there is very little difference, but supposedly there is some sort
of issue with different PIL versions.  What version of PIL do you have?

Ben Root

Hi everyone,

I just committed a big typos fix to trunk (r8925), should changes
like this be backported to the maintenance branch?

best,
-- 
Paul Ivanov
314 address only used for lists,  off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 

Hi,
I was playing with test suite and I noticed that :

morph@zion:~/deb/build-area/matplotlib-1.0.1$
PYTHONPATH=build/lib.linux-x86_64-2.6 python -c "import matplotlib as
m ; m.test(verbosity=1)"
/usr/lib/pymodules/python2.6/nose/plugins/manager.py:391: UserWarning:
Module matplotlib was already imported from
/home/morph/deb/build-area/matplotlib-1.0.1/build/lib.linux-x86_64-2.6/matplotlib/__init__.pyc,
but /usr/lib/pymodules/python2.6 is being added to sys.path
  import pkg_resources
..K........K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..K..KE.K..K..K..K..K..K/home/morph/deb/build-area/matplotlib-1.0.1/build/lib.linux-x86_64-2.6/matplotlib/axes.py:2381:
UserWarning: Attempting to set identical left==right results
in singular transformations; automatically expanding.
left=730139.0, right=730139.0
  + 'left=%s, right=%s') % (left, right))
...K..KK..K..K.....K..K..K..K..K....K..K..K....K..K..K..K..K
======================================================================
ERROR: matplotlib.tests.test_axes.test_pcolormesh
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/nose/case.py", line 183, in runTest
    self.test(*self.arg)
  File "/home/morph/deb/build-area/matplotlib-1.0.1/build/lib.linux-x86_64-2.6/matplotlib/testing/decorators.py",
line 32, in failer
    result = f(*args, **kwargs)
  File "/home/morph/deb/build-area/matplotlib-1.0.1/build/lib.linux-x86_64-2.6/matplotlib/testing/decorators.py",
line 126, in decorated_compare_images
    '(RMS %(rms).3f)'%err)
ImageComparisonFailure: images not close:
/home/morph/deb/build-area/matplotlib-1.0.1/result_images/test_axes/pcolormesh.png
vs. /home/morph/deb/build-area/matplotlib-1.0.1/result_images/test_axes/expected-pcolormesh.png
(RMS 116.512)

----------------------------------------------------------------------
Ran 150 tests in 107.607s

FAILED (KNOWNFAIL=46, errors=1)

Except for the UserWarning, there is an error in the suite: is someone
else able to replicate it? is it another KNOWNFAIL?

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

The problem appends on some paths/polygons, not all. Have a look at
the joined pictures. The to_polygons method normally take care about
polygons holes, but here some vertices are not converted, resulting in
wrong geometries.
#############
import numpy as np
import pylab as plb
a=np.recfromtxt('rpatch3.grid', delimiter='\t',names=True)
lev=np.linspace(a.ux.min(), a.ux.max(), 10)
cs=plb.tricontourf(a.lon, a.lat, a.ux, lev)
path=cs.collections[5].get_paths()[0] #210 vertices
path.to_polygons() #16 vertices :(
#############
Cheers

2011/1/14 Michael Droettboom <md...@st...>:
> It's not obvious to me that this is wrong.  The path has a MOVETO
> command (1) in the middle, and thus should require the creation of two
> polygons.  Can you provide some code or pictures that demonstrate the
> problem?
>
> Mike
>
> On 01/13/2011 05:54 PM, Lionel Roubeyrie wrote:
>> Hi all,
>> Using the last 1.0.1 matplotlib version,sometimes exporting paths to
>> polygons gives wrong results like here (paths come from a
>> tricontourset) :
>> In [94]: path
>> Out[94]:
>> Path([[ 172.0079229   -43.79390934]
>>   [ 171.97660793  -43.785     ]
>>   [ 171.96206864  -43.78273625]
>>   [ 171.959       -43.78114859]
>>   ...
>>   [ 171.593       -44.00678244]
>>   [ 171.64906502  -44.01      ]
>>   [ 171.654       -44.01077106]
>>   [ 171.7068607   -44.0160044 ]], [1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>> 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1 2 2 2 2 2 2 2 2 2
>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2])
>> In [95]: path.vertices.shape
>> Out[95]: (210, 2)
>>
>> but to_polygons gives another result :
>> In [98]: path.to_polygons()
>> Out[98]:
>> [array([[ 172.0079229 ,  -43.79390934],
>>         [ 171.86039224,  -43.65      ],
>>         [ 172.081     ,  -43.54450289],
>>         [ 172.386     ,  -43.57010293],
>>         [ 172.60631978,  -43.67753099],
>>         [ 172.59231502,  -43.71219961],
>>         [ 172.325     ,  -43.78095532],
>>         [ 172.02      ,  -43.79497729]]),
>>   array([[ 171.715     ,  -44.0160044 ],
>>         [ 173.02676111,  -43.92      ],
>>         [ 172.935     ,  -43.53340591],
>>         [ 171.40281884,  -43.70029758],
>>         [ 171.37760645,  -43.94389688],
>>         [ 171.54044973,  -44.0037666 ],
>>         [ 171.7068607 ,  -44.0160044 ],
>>         [ 171.7068607 ,  -44.0160044 ]])]
>>
>> Cheers
>>
>>
>
>
> --
> Michael Droettboom
> Science Software Branch
> Space Telescope Science Institute
> Baltimore, Maryland, USA
>
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>



-- 
Lionel Roubeyrie
lio...@gm...
http://youarealegend.blogspot.com

Thanks for finding this.  Fixed in r8917/r8918.

Mike

On 01/13/2011 06:00 PM, Sandro Tosi wrote:
> Hi,
> as per recent sphinx (I got 1.0.6 where, and with 1.0.1 it worked
> fine), the image 'formats' is loaded as a unicode object, and so it's
> no more a str as previously identified in
> lib/matplotlib/sphinxext/plot_directive.py: the attached patch make
> the doc be buildable again with 1.0.6 and should be backportable.
>
> Cheers,
>    
>
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>    


-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA

It's not obvious to me that this is wrong.  The path has a MOVETO 
command (1) in the middle, and thus should require the creation of two 
polygons.  Can you provide some code or pictures that demonstrate the 
problem?

Mike

On 01/13/2011 05:54 PM, Lionel Roubeyrie wrote:
> Hi all,
> Using the last 1.0.1 matplotlib version,sometimes exporting paths to
> polygons gives wrong results like here (paths come from a
> tricontourset) :
> In [94]: path
> Out[94]:
> Path([[ 172.0079229   -43.79390934]
>   [ 171.97660793  -43.785     ]
>   [ 171.96206864  -43.78273625]
>   [ 171.959       -43.78114859]
>   ...
>   [ 171.593       -44.00678244]
>   [ 171.64906502  -44.01      ]
>   [ 171.654       -44.01077106]
>   [ 171.7068607   -44.0160044 ]], [1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
> 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1 2 2 2 2 2 2 2 2 2
>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>   2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2])
> In [95]: path.vertices.shape
> Out[95]: (210, 2)
>
> but to_polygons gives another result :
> In [98]: path.to_polygons()
> Out[98]:
> [array([[ 172.0079229 ,  -43.79390934],
>         [ 171.86039224,  -43.65      ],
>         [ 172.081     ,  -43.54450289],
>         [ 172.386     ,  -43.57010293],
>         [ 172.60631978,  -43.67753099],
>         [ 172.59231502,  -43.71219961],
>         [ 172.325     ,  -43.78095532],
>         [ 172.02      ,  -43.79497729]]),
>   array([[ 171.715     ,  -44.0160044 ],
>         [ 173.02676111,  -43.92      ],
>         [ 172.935     ,  -43.53340591],
>         [ 171.40281884,  -43.70029758],
>         [ 171.37760645,  -43.94389688],
>         [ 171.54044973,  -44.0037666 ],
>         [ 171.7068607 ,  -44.0160044 ],
>         [ 171.7068607 ,  -44.0160044 ]])]
>
> Cheers
>
>    


-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA

Hello,

I run the test.py example from the folder mplh5canvas/test. This example
generated in the output folder 2 html pages (test.html and
test_rendered.html) and also 2 images (filename.png and filename.svg). The
test.html page is displayed ok, but when I open the test_rendered.html page
the images from the column "H5 Canvas (PNG from Chrome 4.0 OSX)" are not
displayed.

After I studied the source code of the test.py example I saw the following
line:

(line 85)  thtml += "<td><img src='%s' width='%dpx' height='%dpx' />" %
("h5canvas_" + png_filename, w, h)

Now the question is: What is supposed to be "h5canvas_" + png_filename?
There is no image generated with this name in the output folder.

The HTML 5 Canvas Backend was downloaded from here:
http://code.google.com/p/mplh5canvas/downloads/list

Thanks!

Hi,
as per recent sphinx (I got 1.0.6 where, and with 1.0.1 it worked
fine), the image 'formats' is loaded as a unicode object, and so it's
no more a str as previously identified in
lib/matplotlib/sphinxext/plot_directive.py: the attached patch make
the doc be buildable again with 1.0.6 and should be backportable.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Hi all,
Using the last 1.0.1 matplotlib version,sometimes exporting paths to
polygons gives wrong results like here (paths come from a
tricontourset) :
In [94]: path
Out[94]:
Path([[ 172.0079229   -43.79390934]
 [ 171.97660793  -43.785     ]
 [ 171.96206864  -43.78273625]
 [ 171.959       -43.78114859]
 ...
 [ 171.593       -44.00678244]
 [ 171.64906502  -44.01      ]
 [ 171.654       -44.01077106]
 [ 171.7068607   -44.0160044 ]], [1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1 2 2 2 2 2 2 2 2 2
 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2])
In [95]: path.vertices.shape
Out[95]: (210, 2)

but to_polygons gives another result :
In [98]: path.to_polygons()
Out[98]:
[array([[ 172.0079229 ,  -43.79390934],
       [ 171.86039224,  -43.65      ],
       [ 172.081     ,  -43.54450289],
       [ 172.386     ,  -43.57010293],
       [ 172.60631978,  -43.67753099],
       [ 172.59231502,  -43.71219961],
       [ 172.325     ,  -43.78095532],
       [ 172.02      ,  -43.79497729]]),
 array([[ 171.715     ,  -44.0160044 ],
       [ 173.02676111,  -43.92      ],
       [ 172.935     ,  -43.53340591],
       [ 171.40281884,  -43.70029758],
       [ 171.37760645,  -43.94389688],
       [ 171.54044973,  -44.0037666 ],
       [ 171.7068607 ,  -44.0160044 ],
       [ 171.7068607 ,  -44.0160044 ]])]

Cheers

-- 
Lionel Roubeyrie
lio...@gm...
http://youarealegend.blogspot.com

Hi,
Jakub spotted this problem with mpl and new sphinx:

On Tue, Jan 4, 2011 at 20:47, Jakub Wilk <jw...@de...> wrote:
> In Sphinx 1.0, ":param" field can accept up to 2 whitespace-separated
> arguments. Unforunately, this new feature breaks a bit documentation of some
> stuff in the mpl_toolkits.axes_grid.axes_divider module, which is using
> spaces for its own purpose:
>
> $ grep -E -r 'param [^ ]* [^ ]*:' .
> ./lib/mpl_toolkits/axes_grid/axes_divider.py:        :param nx, nx1:
> Integers specifying the column-position of the
> ./lib/mpl_toolkits/axes_grid/axes_divider.py:        :param ny, ny1: same as
> nx and nx1, but for row positions.
> ./lib/mpl_toolkits/axes_grid/axes_divider.py:        :param nx, nx1:
> Integers specifying the column-position of the
> ./lib/mpl_toolkits/axes_grid/axes_divider.py:        :param ny, ny1: same as
> nx and nx1, but for row positions.
> ./lib/mpl_toolkits/axes_grid/axes_divider.py:        :param nx, nx1:
> Integers specifying the column-position of the
> ./lib/mpl_toolkits/axes_grid/axes_divider.py:        :param ny, ny1: same as
> nx and nx1, but for row positions.
>
> [0] See bottom of:
> http://sphinx.pocoo.org/domains.html#info-field-lists

That generates pages like this:

locate(nx, ny, nx1=None, ny1=None, renderer=None)¶
    Parameters:	

        * nx1 (nx,) – Integers specifying the column-position of the
cell. When nx1 is None, a single nx-th column is specified. Otherwise
location of columns spanning between nx to nx1 (but excluding nx1-th
column) is specified.
        * ny1 (ny,) – same as nx and nx1, but for row positions.

With the attached patch, I removed the space between those arguments,
but at least it generates a correct list even tho it's a bit visually
unpleasant.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

On 01/13/2011 09:08 AM, Benjamin Root wrote:
> A fellow student approached me today wanting to know if matplotlib was
> able to produce a certain kind of 3d plot where a filled contour was
> placed on one of the axes panels.  I knew it was possible with regular
> contours, but was surprised when I realized that the same feature wasn't
> available for contourf.  So I wrote a patch to add that feature (and
> clean up a few documentation-related things).  I also added an example
> script with examples/mplot3d/contourf3d_demo2.py.
>
> This is the image produced by the example:
> http://dl.dropbox.com/u/7325604/newcontourf3d.png

Nice!  Thank you!

On a related note, a considerable fraction of the mpl bug tickets on 
sourceforge are for mplot3d.  For a while I was assigning them to 
Reinier Heeres, but I think he has been unable to get to them.  I 
suspect some are actually quite simple to fix, and others may already 
have been fixed by work you have been doing on mplot3d.  If you get a 
chance, please look through them and close any that can be closed.  If 
there are any that you think you will be able to address, but not 
immediately, please assign them to yourself.

Thanks.

Eric

>
> This was committed in r8915.
>
> Enjoy!
> Ben Root