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
(9)
2
(8)
3
4
(6)
5
6
7
(41)
8
(18)
9
(25)
10
(18)
11
(10)
12
(13)
13
(7)
14
(4)
15
(12)
16
(6)
17
(9)
18
(7)
19
(2)
20
(5)
21
(7)
22
(2)
23
(11)
24
(11)
25
(14)
26
(3)
27
(3)
28
(17)
29
(7)
30
(16)
31
(8)


Showing 7 results of 7

From: Edward G. <Edw...@me...> - 2011年03月21日 21:28:06
Following the advice to ping you on the mailing list, I've submitted a 
suggestion for a patch to the EMF Backend. I've copied the contents 
here for convenience.
Patch ID is: 3232997
Content is:
With Matplotlib 1.0.1, When plotting a patch (e.g. text with a bbox with 
facecolor), the facecolor of the patch is passed to the backend as RGBa. 
EMFBrush can't handle RGBa and dies with the following:
File "/usr/local/lib/python2.7/dist-packages/matplotlib/patches.py", 
line 411, in draw
renderer.draw_path(gc, tpath, affine, rgbFace)
File 
"/usr/local/lib/python2.7/dist-packages/matplotlib/backends/backend_emf.py", 
line 260, in draw_path
self.select_brush(rgbFace)
File 
"/usr/local/lib/python2.7/dist-packages/matplotlib/backends/backend_emf.py", 
line 567, in select_brush
brush=EMFBrush(self.emf,rgb)
File 
"/usr/local/lib/python2.7/dist-packages/matplotlib/backends/backend_emf.py", 
line 107, in __init__
r,g,b=rgb
ValueError: too many values to unpack
Suggested patch is to change line 107 in backend_emf.py from r,g,b=rgb to:
r,g,b=rgb[:3]
which will drop the alpha channel. Given the EMF backend doesn't support 
alpha channels, it shouldn't cause any problems to do this silently.
From: johanngoetz <jg...@uc...> - 2011年03月21日 14:26:28
Is there a way to set the style and scilimits to the colorbar axes? All my
attempts failed. For example, run the following script, I get the error
shown below:
### begin example script
import numpy
from matplotlib import pyplot
n = 5000000
x = numpy.random.standard_normal(n)
y = 2.0 + 3.0 * x + 4.0 * numpy.random.standard_normal(n)
xmin = x.min()
xmax = x.max()
ymin = y.min()
ymax = y.max()
hist, edges = numpy.histogramdd([y,x], bins=[25,25],
 range=[[ymin,ymax], [xmin,xmax]])
extent = [xmin, xmax, ymin, ymax]
fig = pyplot.figure()
ax = fig.add_subplot(1,1,1)
plt = ax.imshow(hist,
 extent = extent,
 origin = 'lower',
 interpolation = 'nearest',
 aspect = 'auto')
cb = fig.colorbar(plt, ax=ax)
# This causes an AttributeError exception
cb.ax.ticklabel_format(style='sci', scilimits=(0,4))
pyplot.show()
### end example script
> python cb_scilim_test.py
Traceback (most recent call last):
 File "cb_scilim_test.py", line 25, in <module>
 cb.ax.ticklabel_format(style='sci', scilimits=(0,4))
 File "/usr/lib64/python2.7/site-packages/matplotlib/axes.py", line 2117,
in ticklabel_format
 "This method only works with the ScalarFormatter.")
AttributeError: This method only works with the ScalarFormatter.
-- 
View this message in context: http://old.nabble.com/colorbar-and-scilimits-tp31201133p31201133.html
Sent from the matplotlib - users mailing list archive at Nabble.com.
From: Michiel de H. <mjl...@ya...> - 2011年03月21日 13:14:41
--- On Sun, 3/20/11, Daniel Welling <dan...@gm...> wrote:
> The OSX backend used to have a bug where you cannot type a
> name in the file name text box.Since that has been fixed, ...
That was not a bug in the MacOSX backend (and therefore was not fixed), but is related to how Python is installed on your system: If your Python is not a framework installation, it will not interact correctly with Apple's windowing manager. This is due to OS X itself and is independent of the MacOSX backend.
I
 have found a new bug: every so often, when you go to save a file, the 
"save" and "cancel" button stop responding, trapping the user in file 
saving limbo. I'll have to play with it again to figure out what 
triggers this.
Can you check if your Python is built as a framework? If it is, MacOS.WMAvailable() should return True:
$ python
Python 2.7.1 (r271:86832, Mar 12 2011, 13:44:53) 
[GCC 4.0.1 (Apple Computer, Inc. build 5370)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import MacOS
>>> MacOS.WMAvailable()
True
>>> 
Best,
--Michiel.
 
From: Rohaq <ro...@de...> - 2011年03月21日 04:30:49
I've been visualising some data using the pyplot fill function, and whilst
overlapping polygons do mix their colours and allow for any overlaps to be
apparent, I thought that perhaps this would look much better in a heatmap
format to better show high levels of change in the same areas.
I've tested this using the histogram2d function in numpy using various
online examples, and whilst experiments with random data looked nice enough,
each set of results data is basically a series of 0's and 1's: In a heatmap
using the same code, this results in an incredibly long (since there's about
65000 results) heatmap that's only a pixel or two in height. Also, I can't
seem to use the tools to zoom in and navigate around this, which is pretty
much a requirement given the large number of data rows.
Does anyone know if there's a way to convert a series of polygon objects
into a decent looking heatmap? Any help is appreciated!
Cheers!
*Rohaq*
From: Daniel W. <dan...@gm...> - 2011年03月21日 02:32:42
Hello, Michiel.
The OSX backend used to have a bug where you cannot type a name in the file
name text box. Since that has been fixed, I have found a new bug: every so
often, when you go to save a file, the "save" and "cancel" button stop
responding, trapping the user in file saving limbo. I'll have to play with
it again to figure out what triggers this. Other than that, the OSX backend
is light and quick, which is nice. When QT4 is working, however, I prefer
that. Sorry I can't give you more details; I'll see if I can get a clearer
picture.
-dw
On Sun, Mar 20, 2011 at 1:31 AM, Michiel de Hoon <mjl...@ya...>wrote:
> --- On *Wed, 3/16/11, Daniel Welling <dan...@gm...>* wrote:
>
> After playing with backends quite a bit, I have found that the best one in
> terms of speed, robustness, and features is Qt4Agg - especially on OSX,
> where the MacOSX backend is buggy and many others just don't plain work.
>
> Why do you think that the MacOSX backend is buggy?
>
> --Michiel.
>
>
>
>
>
>
From: Darren D. <dsd...@gm...> - 2011年03月21日 01:59:35
On Sun, Mar 20, 2011 at 8:52 PM, Xavier Gnata <xav...@gm...> wrote:
> On 03/20/2011 07:19 PM, Darren Dale wrote:
>>
>> On Sun, Mar 20, 2011 at 2:08 PM, Xavier Gnata<xav...@gm...>
>> wrote:
>>>
>>> Hi,
>>>
>>> It looks like the
>>> http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/branches/py3k/
>>> in dead.
>>> The last commit was 8months ago.
>>>
>>> Numpy is ok with python3.1, scipy is ok, nose is ok, ipython is usable.
>>> Ubuntu already provides python-tk for python3.x
>>> It would be nice to port matplotlib to python3.
>>> Is there a plan? another svn/git branch?
>>
>> https://github.com/matplotlib/matplotlib-py3
>
> Thanks!
> AFAICS it works already well with the tk backend :)
> Are you interested in more testing with another backend?
Mike D. put a wiki page together summarizing where things stand and
listing outstanding issues:
https://github.com/matplotlib/matplotlib-py3/wiki
From: Xavier G. <xav...@gm...> - 2011年03月21日 00:53:07
On 03/20/2011 07:19 PM, Darren Dale wrote:
> On Sun, Mar 20, 2011 at 2:08 PM, Xavier Gnata<xav...@gm...> wrote:
>> Hi,
>>
>> It looks like the
>> http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/branches/py3k/
>> in dead.
>> The last commit was 8months ago.
>>
>> Numpy is ok with python3.1, scipy is ok, nose is ok, ipython is usable.
>> Ubuntu already provides python-tk for python3.x
>> It would be nice to port matplotlib to python3.
>> Is there a plan? another svn/git branch?
> https://github.com/matplotlib/matplotlib-py3
Thanks!
AFAICS it works already well with the tk backend :)
Are you interested in more testing with another backend?
Xavier

Showing 7 results of 7

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 によって変換されたページ (->オリジナル) /