SourceForge logo
SourceForge logo
Menu

matplotlib-users — Discussion related to using matplotlib

You can subscribe to this list here.

2003 Jan
Feb
Mar
Apr
May
(3)
Jun
Jul
Aug
(12)
Sep
(12)
Oct
(56)
Nov
(65)
Dec
(37)
2004 Jan
(59)
Feb
(78)
Mar
(153)
Apr
(205)
May
(184)
Jun
(123)
Jul
(171)
Aug
(156)
Sep
(190)
Oct
(120)
Nov
(154)
Dec
(223)
2005 Jan
(184)
Feb
(267)
Mar
(214)
Apr
(286)
May
(320)
Jun
(299)
Jul
(348)
Aug
(283)
Sep
(355)
Oct
(293)
Nov
(232)
Dec
(203)
2006 Jan
(352)
Feb
(358)
Mar
(403)
Apr
(313)
May
(165)
Jun
(281)
Jul
(316)
Aug
(228)
Sep
(279)
Oct
(243)
Nov
(315)
Dec
(345)
2007 Jan
(260)
Feb
(323)
Mar
(340)
Apr
(319)
May
(290)
Jun
(296)
Jul
(221)
Aug
(292)
Sep
(242)
Oct
(248)
Nov
(242)
Dec
(332)
2008 Jan
(312)
Feb
(359)
Mar
(454)
Apr
(287)
May
(340)
Jun
(450)
Jul
(403)
Aug
(324)
Sep
(349)
Oct
(385)
Nov
(363)
Dec
(437)
2009 Jan
(500)
Feb
(301)
Mar
(409)
Apr
(486)
May
(545)
Jun
(391)
Jul
(518)
Aug
(497)
Sep
(492)
Oct
(429)
Nov
(357)
Dec
(310)
2010 Jan
(371)
Feb
(657)
Mar
(519)
Apr
(432)
May
(312)
Jun
(416)
Jul
(477)
Aug
(386)
Sep
(419)
Oct
(435)
Nov
(320)
Dec
(202)
2011 Jan
(321)
Feb
(413)
Mar
(299)
Apr
(215)
May
(284)
Jun
(203)
Jul
(207)
Aug
(314)
Sep
(321)
Oct
(259)
Nov
(347)
Dec
(209)
2012 Jan
(322)
Feb
(414)
Mar
(377)
Apr
(179)
May
(173)
Jun
(234)
Jul
(295)
Aug
(239)
Sep
(276)
Oct
(355)
Nov
(144)
Dec
(108)
2013 Jan
(170)
Feb
(89)
Mar
(204)
Apr
(133)
May
(142)
Jun
(89)
Jul
(160)
Aug
(180)
Sep
(69)
Oct
(136)
Nov
(83)
Dec
(32)
2014 Jan
(71)
Feb
(90)
Mar
(161)
Apr
(117)
May
(78)
Jun
(94)
Jul
(60)
Aug
(83)
Sep
(102)
Oct
(132)
Nov
(154)
Dec
(96)
2015 Jan
(45)
Feb
(138)
Mar
(176)
Apr
(132)
May
(119)
Jun
(124)
Jul
(77)
Aug
(31)
Sep
(34)
Oct
(22)
Nov
(23)
Dec
(9)
2016 Jan
(26)
Feb
(17)
Mar
(10)
Apr
(8)
May
(4)
Jun
(8)
Jul
(6)
Aug
(5)
Sep
(9)
Oct
(4)
Nov
Dec
2017 Jan
(5)
Feb
(7)
Mar
(1)
Apr
(5)
May
Jun
(3)
Jul
(6)
Aug
(1)
Sep
Oct
(2)
Nov
(1)
Dec
2018 Jan
Feb
Mar
Apr
(1)
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
2020 Jan
Feb
Mar
Apr
May
(1)
Jun
Jul
Aug
Sep
Oct
Nov
Dec
2025 Jan
(1)
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
S M T W T F S



1
(3)
2
(5)
3
(11)
4
5
6
(8)
7
(4)
8
(4)
9
(2)
10
(4)
11
(1)
12
(3)
13
(3)
14
(5)
15
(11)
16
(8)
17
(5)
18
(3)
19
(1)
20
(6)
21
(7)
22
(5)
23
(6)
24
(4)
25
(5)
26
27
(1)
28
(13)
29
(4)
30
(2)
31
(8)

Showing 2 results of 2

From: algotr8der <alg...@gm...> - 2013年05月09日 19:55:45
I tried to execute the following code:
http://matplotlib.org/faq/howto_faq.html#test-whether-a-point-is-inside-a-polygon
However I get errors I describe here:
http://stackoverflow.com/questions/16452509/matplotlib-pnpoly-example-results-in-error
>>>import numpy as np
>>>import matplotlib.nxutils as nx
>>>verts = np.array([ [0,0], [0, 1], [1, 1], [1,0]], float)
>>>nx.pnpoly(0.5, 0.5, verts)
Traceback (most recent call last):
 File "<console>", line 1, in <module>
 File "C:\Python27\lib\site-packages\matplotlib\nxutils.py", line 26, in
pnpoly
 return p.contains_point(x, y)
 File "C:\Python27\lib\site-packages\matplotlib\path.py", line 289, in
contains_point
 transform = transform.frozen()
AttributeError: 'float' object has no attribute 'frozen'
>>>nx.pnpoly(0.5, 1.5, verts)
Traceback (most recent call last):
 File "<console>", line 1, in <module>
 File "C:\Python27\lib\site-packages\matplotlib\nxutils.py", line 26, in
pnpoly
 return p.contains_point(x, y)
 File "C:\Python27\lib\site-packages\matplotlib\path.py", line 289, in
contains_point
 transform = transform.frozen()
AttributeError: 'float' object has no attribute 'frozen'
Apparently, nxutils is deprecated, which to me means it should still work
but a user on stackoverflow pointed out that there may be some code rot.
That said, the documentation on matplotlib.path.Path.contains_point is weak
(see below). Does anyone have an example of how I can do the exact same
thing in the code in the howto_faq but using the suggested function
(contains_point)?
http://matplotlib.org/1.2.1/api/path_api.html?highlight=contains_point#matplotlib.path.Path.contains_point
contains_point(point, transform=None, radius=0.0)
 Returns True if the path contains the given point.
 If transform is not None, the path will be transformed before performing
the test.
 radius allows the path to be made slightly larger or smaller.
contains_points(points, transform=None, radius=0.0)
 Returns a bool array which is True if the path contains the
corresponding point.
 If transform is not None, the path will be transformed before performing
the test.
 radius allows the path to be made slightly larger or smaller.
--
View this message in context: http://matplotlib.1069221.n5.nabble.com/re-matplotlib-pnpoly-example-results-in-error-tp41028.html
Sent from the matplotlib - users mailing list archive at Nabble.com.
From: Jae-Joon L. <lee...@gm...> - 2013年05月09日 02:49:18
ImageGrid creates axes for colobar even if cbar_mode=None. These axes for
colorbar are set to invisible, so usually they are harmless.
tight_layout, however, do not care whether the axes is visible or not, and
the warning is because of these "invisible" axes for colorbars.
For comparison, if you turn on all colorbar with cbar_mode="each", the
warning will go away.
You may manually remove colorbar axes from the figure if you want,
```
for ax in grid.cbar_axes: fig._axstack.remove(ax)
```
but do this only when cbar_mode=None.
So, I think the warning is harmless.
I will make a pull request that make tight_layout to ignore any invisible
axes soon.
Regards,
-JJ
On Wed, May 8, 2013 at 10:21 PM, Jonathan Slavin <js...@cf...>wrote:
> Hi,
>
> I wrote a short routine to look through a set of images that result from
> slightly different processing of the same data. I want to compare three
> different images and be able to zoom them all in the same way and then
> move onto the next set of three. The best way that I've found to do
> that so far involves using mpl_toolkits.axes_grid1.ImageGrid. It all
> works fine. I found that to get the most image on screen at once, using
> the tight_layout=True argument to plt.figure gives excellent results.
> My one question is that I get the following warning:
>
> WARNING: This figure includes Axes that are not compatible with
> tight_layout, so its results might be incorrect. [matplotlib.figure]
>
> As I say, the results are good, so it's not really a problem, but I do
> wonder about the source of the warngin -- and whether re-using the code
> in a different way in the future could lead to problems. So, my
> question is: what is the problem pointed to by the warning and how could
> I avoid it (while still getting the same good results)?
>
> Regards,
> Jon
> --
> ______________________________________________________________
> Jonathan D. Slavin Harvard-Smithsonian CfA
> js...@cf... 60 Garden Street, MS 83
> phone: (617) 496-7981 Cambridge, MA 02138-1516
> cell: (781) 363-0035 USA
> ______________________________________________________________
>
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and
> their applications. This 200-page book is written by three acclaimed
> leaders in the field. The early access version is available now.
> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Showing 2 results of 2

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X





Briefly describe the problem (required):
Upload screenshot of ad (required):
Select a file, or drag & drop file here.
Screenshot instructions:

Click URL instructions:
Right-click on the ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Ad destination/click URL:

AltStyle によって変換されたページ (->オリジナル) /