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






Showing results of 428

<< < 1 .. 14 15 16 17 18 > >> (Page 16 of 18)
From: Friedrich R. <fri...@gm...> - 2010年10月04日 20:27:07
2010年10月4日 Nicolas Rougier <Nic...@lo...>:
> I'm trying to have animated plots using draw_artist on mac os x and I got an error with the following script:
>
> import numpy as np
> import matplotlib.pyplot as plt
>
> plt.ion()
> plt.figure()
> subplot = plt.subplot(1,1,1)
> axis = plt.imshow(np.random.random((10,10)))
> plt.draw()
> subplot.draw_artist(axis)
> plt.show()
>
> The traceback is:
>
> Traceback (most recent call last):
> File "matplotlib-bug.py", line 8, in <module>
>  subplot.draw_artist(axis)
> File "/Volumes/Data/Local/lib/python2.7/site-packages/matplotlib/axes.py", line 1946, in draw_artist
>  a.draw(self._cachedRenderer)
> File "/Volumes/Data/Local/lib/python2.7/site-packages/matplotlib/artist.py", line 55, in draw_wrapper
>  draw(artist, renderer, *args, **kwargs)
> File "/Volumes/Data/Local/lib/python2.7/site-packages/matplotlib/image.py", line 338, in draw
>  gc = renderer.new_gc()
> File "/Volumes/Data/Local/lib/python2.7/site-packages/matplotlib/backends/backend_macosx.py", line 105, in new_gc
>  self.gc.save()
> RuntimeError: CGContextRef is NULL
>
>
> Is there something wrong in my script (it seems to be working on linux) ?
I don't know what it is, and it looks like some problem with the
Mac-native backend, but I believe you can sort it out by just
switching the backend to e.g. TkAgg.
Friedrich
From: Friedrich R. <fri...@gm...> - 2010年10月04日 20:10:04
> """
> First attempt at a histogram strip chart (made up name).
> if-main block taken from [1] except that I've replaced uniform distributions
> with normal distributions.
> [1] http://matplotlib.sourceforge.net/examples/pylab_examples/boxplot_demo3.html
> """
> import numpy as np
> import matplotlib.pyplot as plt
> from matplotlib import collections
>
> NORM_TYPES = dict(max=max, sum=sum)
> class BinCollection(collections.PatchCollection):
>   def __init__(self, hist, bin_edges, x=0, width=1, cmap=plt.cm.gray_r,
>         norm_type='max', **kwargs):
>     yy = (bin_edges[:-1] + bin_edges[1:])/2.
>     heights = np.diff(bin_edges)
>     bins = [plt.Rectangle((x, y), width, h) for y, h in zip(yy, heights)]
>     norm = NORM_TYPES[norm_type]
>     fc = cmap(np.asarray(hist, dtype=float)/norm(hist))
>     super(BinCollection, self).__init__(bins, facecolors=fc, **kwargs)
Is this equivalent to writing collections.PatchCollection.__init__()
and what are the advantages of super()?
I think you can use axes.pcolor() to replace BinCollection. pcolor()
just adds a collection similar to what you do now by hand for you.
With appropriate arguments it should do the job. You can also look
into pcolorfast() and pcolormesh().
> def histstrip(x, positions=None, widths=None, ax=None):
>   if ax is None:
>     ax = plt.gca()
>   if positions is None:
>     positions = range(1, len(x) + 1)
>   if widths is None:
>     widths = np.min(np.diff(positions)) / 2. * np.ones(len(positions))
>   for data, x_pos, w in zip(x, positions, widths):
>     x_pos -= w/2.
>     hist, bin_edges = np.histogram(data)
No other arguments to numpy.histogram() allowed?
>     bins = BinCollection(hist, bin_edges, width=w, x=x_pos)
>     ax.add_collection(bins, autolim=True)
>   ax.set_xticks(positions)
>   ax.autoscale_view()
> if __name__ == '__main__':
>   import matplotlib.pyplot as plt
>   import numpy as np
>   np.random.seed(2)
>   inc = 0.1
>   e1 = np.random.normal(0,1, size=(500,))
>   e2 = np.random.normal(0,1, size=(500,))
>   e3 = np.random.normal(0,1 + inc, size=(500,))
>   e4 = np.random.normal(0,1 + 2*inc, size=(500,))
>   treatments = [e1,e2,e3,e4]
>   fig, ax = plt.subplots()
>   pos = np.array(range(len(treatments)))+1
>   histstrip(treatments, ax=ax)
>   ax.set_xlabel('treatment')
>   ax.set_ylabel('response')
>   fig.subplots_adjust(right=0.99,top=0.99)
>   plt.show()
In my opinion this is too special to be added as a general matplotlib
plotting feature.
Friedrich
From: Benjamin R. <ben...@ou...> - 2010年10月04日 20:05:18
On Mon, Oct 4, 2010 at 2:21 PM, Erik Tollerud <eri...@gm...>wrote:
> I've noticed some odd behavior in the mplot3d toolkit when using
> scatter3D with plot_surface. What I want to do is generate the
> surface with an alpha level of 0.5, such that any points that are
> between me and the surface should come out fully opaque, and any
> points behind the surface should be rendered blended with the surface.
> Instead, the scattered points are blended with the surface regardless
> of whether they are in front of it or behind. There's also a weird
> behavior where, depending on the viewing angle, the points will
> suddenly snap from fully opaque (even if behind the surface) to
> transparent. An example is attached, with renderings of the two
> states in the URLs below.
>
> Is this a bug, or am I doing something wrong?
>
> http://dl.dropbox.com/u/8683962/mpl3dalpha-1.png
> http://dl.dropbox.com/u/8683962/mpl3dalpha-2.png
>
> --
> Erik Tollerud
>
>
At first glance, I wonder if this is just because of mplot3d's naive
approach of figuring out what is behind other things. mplot3d doesn't do
any sort of physics or ray-tracing to figure out how elements are positioned
relative to the camera. Try it again with perfectly opaque surface and
dots, and I bet you will have dots "magically" appearing in front of the
surface at certain viewing angles and then disappearing.
Note, I have only looked at the photos, not the code.
Ben Root
From: Benjamin R. <ben...@ou...> - 2010年10月04日 19:58:53
On Mon, Oct 4, 2010 at 1:57 PM, Waléria Antunes David <
wal...@gm...> wrote:
> Hi all,
>
> My problem is this error: http://pastebin.com/bfu29WuF<http://pastebin.com/ZPzdC5c8>
>
> my code: http://pastebin.com/KzwEmucN
>
> What could be?
>
> Thanks
> Waleria
>
Waleria,
I am not entirely familiar with programming python in a Windows environment,
however, you are attempting to open files with the name: 'C:\date1.dat'.
The backslash is probably acting as an escape character and causing the
filename to be interpreted differently from how you expect. Try this:
x, y, yerr = np.loadtxt(r'C:\date1.dat', unpack=True)
The 'r' before the string forces python to not interpret any special
characters in a special way. Also note that I simplified your data loading
code with the use of the 'unpack=True' keyword argument.
I hope this helps,
Ben Root
From: Tony S Yu <ts...@gm...> - 2010年10月04日 19:51:58
On Oct 4, 2010, at 3:14 PM, Jouni K. Seppänen wrote:
> Tony S Yu <ts...@gm...> writes:
> 
>> This is probably unrelated, but I can't even use serif fonts on the
>> MacOSX backend (it just shows up as sans-serif). I tried Times New
>> Roman, Vera, and a Computer Modern unicode font that I normally use).
> 
> I noticed that I didn't really get Vera either, probably because I don't
> have it installed via the usual OS X way, and the MacOSX backend only
> uses fonts that it can find via CTFontCreateWithName or
> ATSFontFindFromPostScriptName, depending on the OS X version it's
> compiled for. Do you see these fonts in Font Book?
Both Times New Roman and CMU show up in Font Book. (There's also a Bitstream Vera font there, but it's different from the one Matplotlib uses.)
Like I said, this is probably a separate issue. I don't want to distract from the issue Joey raised---especially since I don't normally use the MacOSX backend.
-Tony
From: Friedrich R. <fri...@gm...> - 2010年10月04日 19:46:23
Yaaa, this was some time ago, I guess you did the following:
* export CC=gcc-4.2
* export MACOSX_DEPLOYMENT_TARGET=....
* maybe also modifying the setupext.py
I must say, that Python distutils (or distribute, whatever you use)
overrides the CC environment variable with the gcc version Python was
compiled with. If you use python.org Python, this will be gcc-4.0.
Could be that this is your issue: You compiled freetype with gcc-4.2
and Python uses gcc-4.0 for compiling matplotlib. Then the matplotlib
libraries cannot load the gcc-4.2 compiled ones, because they are "too
new". Encountered this several times on my own computer.
Notice that the setupext.py instructions are still valid. The
_png.cpp instructions are obsolete for recent versions of matplotlib,
you can use libpng-1.4 right away.
First, I'll wait for your response if you use python.org Python, and
then we see what to do next. Don't want to bombard you with
non-applicable recommendations.
Concerning your message:
2010年10月3日 Åke Kullenberg <ake...@gm...>:
> I just installed matplotlib-1.0.0 on my system (Snow Leopard, python 2.7),
> but somehow when I try to import pyplot i get the error below.
> For reference, I installed matplotlib from source. Prior to that I installed
> libpng-1.4.4 and freetype-2.4.2 the usual way (./configure, make, make
> install) plus I installed pkgcong as well. After getting the error I tried
> the tips Friedrich R gave in this thread
> (http://old.nabble.com/Symbol-not-found-td28994434.html) too, but I still
> get the error.
Notice, I'm using Python 2.6, I hope this won't be an issue. Using
Snow Leopard as well.
> From a few google attempts it seems that it is an issue of dynamic vs static
> linking. I can't say that I know what that is, but I'd be very interested in
> knowing whether I can do anything from my side to sort things out.
Hmm, here maybe you also ran across what I said, just to add that
afaict make.osx isn't doing static linking, but rather linking against
newly-installed shared libs. The libs are compiled just by the
make.osx script. Got this impression when I had an own look into the
script.
> Here is the error:
>   from matplotlib import ft2font
> ImportError:
> dlopen(/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/ft2font.so,
> 2): Symbol not found: _FT_Attach_File
>  Referenced from:
> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/ft2font.so
>  Expected in: dynamic lookup
Yeah, this looks pretty much like what I said.
Sorry for the confusion with the old threads, I think best will be to
search the matplotlib archive for recent threads, my replies got
better with time, as I sorted out things myself. I really feel I
should write things up for the matplotlib page as far as I came so far
with my investigations ... And please reply back.
If the external libraries you're using change: Do a new build in a
new, freshly untared matplotlib directory or sth like that. I found
that, for some reason, it is necessary to really rebuild the
matplotlib libraries when a shared library they load is changed. It
is not sufficient to just replace the external shared library (like
freetype2) to make it work. My knowledge in linking is not as deep as
that I could explain the guts why this is so, but you have to do it (I
had to at least). Keep in mind that dependency checks do not include
the shared libs matplotlib libraries like ft2font rely on. I can only
guess that it only applies to the gcc-4.0/4.2 issue. Otherwise shared
libs would be nearly useless.
Friedrich
From: Erik T. <eri...@gm...> - 2010年10月04日 19:21:31
Attachments: surfscat3d.py
I've noticed some odd behavior in the mplot3d toolkit when using
scatter3D with plot_surface. What I want to do is generate the
surface with an alpha level of 0.5, such that any points that are
between me and the surface should come out fully opaque, and any
points behind the surface should be rendered blended with the surface.
 Instead, the scattered points are blended with the surface regardless
of whether they are in front of it or behind. There's also a weird
behavior where, depending on the viewing angle, the points will
suddenly snap from fully opaque (even if behind the surface) to
transparent. An example is attached, with renderings of the two
states in the URLs below.
Is this a bug, or am I doing something wrong?
http://dl.dropbox.com/u/8683962/mpl3dalpha-1.png
http://dl.dropbox.com/u/8683962/mpl3dalpha-2.png
-- 
Erik Tollerud
From: Jouni K. S. <jk...@ik...> - 2010年10月04日 19:14:47
Tony S Yu <ts...@gm...> writes:
> This is probably unrelated, but I can't even use serif fonts on the
> MacOSX backend (it just shows up as sans-serif). I tried Times New
> Roman, Vera, and a Computer Modern unicode font that I normally use).
I noticed that I didn't really get Vera either, probably because I don't
have it installed via the usual OS X way, and the MacOSX backend only
uses fonts that it can find via CTFontCreateWithName or
ATSFontFindFromPostScriptName, depending on the OS X version it's
compiled for. Do you see these fonts in Font Book?
-- 
Jouni K. Seppänen
http://www.iki.fi/jks
From: Jouni K. S. <jk...@ik...> - 2010年10月04日 19:09:20
Joey Richards <jo...@ca...> writes:
> The system-installed fonts all should have the minus sign, though I
> don't know for sure which fonts matplotlib is using.
You can find out with dtrace: start up python as usual but don't plot
anything yet, then in another terminal type "ps a" to find out the PID
of the process and trace it with dtruss:
sudo dtruss -p 29611 |& grep Fonts
Here 29611 is the PID. When you plot something, you should see the
process access some files, e.g.
open("/Library/Fonts/Times New Roman.ttf0円", 0x0, 0x0)		 = 12 0
-- 
Jouni K. Seppänen
http://www.iki.fi/jks
From: Tony S Yu <ts...@gm...> - 2010年10月04日 19:07:47
On Oct 4, 2010, at 2:56 PM, Jouni K. Seppänen wrote:
> Joey Richards <jo...@ca...> writes:
> 
>> When I plot with the MacOSX backend using a serif font, the negative
>> signs on the axis labels show up as the "missing glyph" open squares
>> rather than minus signs.
> 
>> I am using matplotlib 1.0 installed from the dmg file for Python 2.6
>> on OSX 10.6. I'm using Python 2.6.6 installed from the python.org
>> binary distribution.
> 
> FWIW, I can't reproduce this on OS X 10.6.4, system Python 2.6.1,
> self-compiled trunk matplotlib, tried Vera and Times New Roman.
This is probably unrelated, but I can't even use serif fonts on the MacOSX backend (it just shows up as sans-serif). I tried Times New Roman, Vera, and a Computer Modern unicode font that I normally use).
In contrast, serif fonts work fine with TkAgg and Qt4Agg on my system (OS X 10.6.4, system Python 2.6.1, matplotlib trunk).
-Tony
From: Waléria A. D. <wal...@gm...> - 2010年10月04日 18:57:39
Hi all,
My problem is this error:
http://pastebin.com/bfu29WuF<http://pastebin.com/ZPzdC5c8>
my code: http://pastebin.com/KzwEmucN
What could be?
Thanks
Waleria
From: Jouni K. S. <jk...@ik...> - 2010年10月04日 18:56:54
Joey Richards <jo...@ca...> writes:
> When I plot with the MacOSX backend using a serif font, the negative
> signs on the axis labels show up as the "missing glyph" open squares
> rather than minus signs.
> I am using matplotlib 1.0 installed from the dmg file for Python 2.6
> on OSX 10.6. I'm using Python 2.6.6 installed from the python.org
> binary distribution.
FWIW, I can't reproduce this on OS X 10.6.4, system Python 2.6.1,
self-compiled trunk matplotlib, tried Vera and Times New Roman.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks
On Oct 4, 2010, at 6:54 AM, Michael Droettboom wrote:
> On 09/17/2010 08:57 PM, Joey Richards wrote:
>> Hello. First, let me apologize if this has been covered---I tried to search the mailing list archives but was unable to get that to work (even queries that should have returned many hits were returning nothing).
>> 
>> When I plot with the MacOSX backend using a serif font, the negative signs on the axis labels show up as the "missing glyph" open squares rather than minus signs.
>> 
>> Things that work around the problem:
>> - disabling the unicode minus sign via axes.unicode_minus: False in the matplotlibrc file (though this obviously gives a hyphen instead of a true minus sign)
>> - switching to a sans-serif font
>> - switching to TkAgg or wxAgg backends
>> - using the text.usetex option
>> 
>> Things that don't work:
>> - switching to a different serif font (at least among Times, Times New Roman, and Bitstream Vera Serif)
>> 
> FWIW, Bitstream Vera Serif (at least the one distributed with 
> matplotlib) does have the minus sign (at codepoint U2212), so I don't 
> think it's the fault of the font. I'm on Linux and don't have Apple's 
> Times or Times New Roman, so I can't verify those.
> 
> This sounds like a bug in the Mac OS-X backend in how it's handling 
> Unicode characters -- though that doesn't explain why the sans-serif 
> font is working.
> 
> Do you have any customizations related to fonts in your matplotlibrc file?
> 
I've set the fonts to use (via font.serif, font.sans-serif, etc) and the font family (via font.family), and the size (via font.size), but commenting those out doesn't seem to help. The system-installed fonts all should have the minus sign, though I don't know for sure which fonts matplotlib is using.
joey
From: Jouni K. S. <jk...@ik...> - 2010年10月04日 18:35:40
Michael Droettboom <md...@st...> writes:
> On 10/02/2010 01:39 PM, Jouni K. Seppänen wrote:
>> Benjamin Root<ben...@ou...> writes:
>>
>> 
>>> And yet, we still allow for saving to jpegs.
>>> 
>> Wow, I didn't know. Last time I tried that I got a traceback, and
>> assumed that it was not supported exactly because jpeg is a nonsensical
>> format for most graphs.
>>
>> I just tried again, and got "TypeError: 'int' object is unsubscriptable"
>> from PIL/JpegImagePlugin.pyc in _save(im, fp, filename). I suppose this
>> doesn't get much testing.
>> 
> Aside from the question of whether we "should" support JPEGs, etc., that 
> code path should work (and in fact it does on my machine). What version 
> of PIL do you have installed, and can you provide the full traceback 
> here? 
It seems that I have an egg install of version 1.1.6., and here's a
traceback:
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
 File "/Users/jks/Hacking/mpl/git/lib/matplotlib/pyplot.py", line 363, in savefig
 return fig.savefig(*args, **kwargs)
 File "/Users/jks/Hacking/mpl/git/lib/matplotlib/figure.py", line 1160, in savefig
 self.canvas.print_figure(*args, **kwargs)
 File "/Users/jks/Hacking/mpl/git/lib/matplotlib/backend_bases.py", line 1961, in print_figure
 **kwargs)
 File "/Users/jks/Hacking/mpl/git/lib/matplotlib/backend_bases.py", line 1787, in print_jpg
 return image.save(filename_or_obj, **kwargs)
 File "/Library/Python/2.6/site-packages/PIL/Image.py", line 1405, in save
 save_handler(self, fp, filename)
 File "/Library/Python/2.6/site-packages/PIL/JpegImagePlugin.py", line 406, in _save
 dpi[0], dpi[1]
TypeError: 'int' object is unsubscriptable
It looks like something is now passing a dpi keyword argument to
print_jpg, but something inside PIL is expecting its value to be a
sequence. I'll commit a fix.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks
From: Nicolas R. <Nic...@lo...> - 2010年10月04日 16:56:41
I'm trying to have animated plots using draw_artist on mac os x and I got an error with the following script:
import numpy as np
import matplotlib.pyplot as plt
plt.ion()
plt.figure()
subplot = plt.subplot(1,1,1)
axis = plt.imshow(np.random.random((10,10)))
plt.draw()
subplot.draw_artist(axis)
plt.show()
The traceback is:
Traceback (most recent call last):
 File "matplotlib-bug.py", line 8, in <module>
 subplot.draw_artist(axis)
 File "/Volumes/Data/Local/lib/python2.7/site-packages/matplotlib/axes.py", line 1946, in draw_artist
 a.draw(self._cachedRenderer)
 File "/Volumes/Data/Local/lib/python2.7/site-packages/matplotlib/artist.py", line 55, in draw_wrapper
 draw(artist, renderer, *args, **kwargs)
 File "/Volumes/Data/Local/lib/python2.7/site-packages/matplotlib/image.py", line 338, in draw
 gc = renderer.new_gc()
 File "/Volumes/Data/Local/lib/python2.7/site-packages/matplotlib/backends/backend_macosx.py", line 105, in new_gc
 self.gc.save()
RuntimeError: CGContextRef is NULL
Is there something wrong in my script (it seems to be working on linux) ?
Information:
matplotlib version: 1.0.0
python version 2.7
macosx version: 10.6.4
Nicolas
From: Jeff W. <js...@fa...> - 2010年10月04日 14:36:45
 On 10/4/10 3:36 AM, nickj wrote:
> Hello all,
>
> I'm playing with Matplotlib & Basemap for the first time, and 
> attempting to render data from the NOAA GFS models. With joy I finally 
> got something on screen, however I was wondering what I might be able 
> to do, to better improve the contour rendering of the final map. To 
> better illustrate my problem, here is a screenshot with added red 
> lines pointing to the odd slicing I get around the contours: 
> http://www.bigoceans.com/slices.png
>
> Is there any way to rectify that?
>
Nick: Are you using matplotlib 1.0.0? I'm not sure, but I think there 
were some improvements to contour in that release which fixed this 
problem. If you are using 1.0.0, could you post the script so I can try it?
> Also, part of my project is to output massively high resolution images 
> of this work, which I'll be using to display in a number of mediums 
> which are of particular aesthetic importance (I'm not a scientist, I'm 
> producing something more in the realm of infographics). I decided 
> perhaps the best method to achieve this is as a PDF/Vector output, 
> which I could generate bitmaps at a later date at any resolution I 
> choose to render the PDF as (upwards of 8000pixels). Would anyone be 
> able to best recommend how I can achieve the highest possible 
> contouring, country borders and other things related to detail? I have 
> attempted to use the resolution=full keyword, however my computer 
> balked and failed to respond after five minutes. What is this keyword 
> actually doing? What can I do to get the greatest resolution of 
> coastline & map representation?
The default is ='c' (or 'crude' which gives very low resolution 
coastlines). Moving upward in resolution, there is 'l','i','h' and 
finally 'f', which is probably overkill for a domain of this size (it 
will be very slow and use a lot of memory).
-Jeff
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
Meteorologist FAX : (303)497-6449
NOAA/OAR/PSD R/PSD1 Email : Jef...@no...
325 Broadway Office : Skaggs Research Cntr 1D-113
Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg
From: Michael D. <md...@st...> - 2010年10月04日 13:55:57
There is a fix for this in SVN in r8712 that will make it into the next 
release.
In the meantime, as a workaround, you can safely delete the font cache 
file in
~/.matplotlib/fontList.cache
Mike
On 10/04/2010 08:44 AM, Matthieu Brucher wrote:
> Hello,
>
> I ahve several installation of matplotlib on several computers with
> different OS but the same HOME directory.
> Matplotlib caches a lot of stuff in ~/.matplotlib, like fonts, but
> they are not located in the same folder in different computers I use.
> The issue is that the cache makes matplotlib raise an exception at
> import time. Would it be possible not to use the cache if the fonts
> mentioned int he cache are not available?
>
> Matthieu
> 
-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA
From: Michael D. <md...@st...> - 2010年10月04日 13:54:09
On 09/17/2010 08:57 PM, Joey Richards wrote:
> Hello. First, let me apologize if this has been covered---I tried to search the mailing list archives but was unable to get that to work (even queries that should have returned many hits were returning nothing).
>
> When I plot with the MacOSX backend using a serif font, the negative signs on the axis labels show up as the "missing glyph" open squares rather than minus signs.
>
> Things that work around the problem:
> - disabling the unicode minus sign via axes.unicode_minus: False in the matplotlibrc file (though this obviously gives a hyphen instead of a true minus sign)
> - switching to a sans-serif font
> - switching to TkAgg or wxAgg backends
> - using the text.usetex option
>
> Things that don't work:
> - switching to a different serif font (at least among Times, Times New Roman, and Bitstream Vera Serif)
> 
FWIW, Bitstream Vera Serif (at least the one distributed with 
matplotlib) does have the minus sign (at codepoint U2212), so I don't 
think it's the fault of the font. I'm on Linux and don't have Apple's 
Times or Times New Roman, so I can't verify those.
This sounds like a bug in the Mac OS-X backend in how it's handling 
Unicode characters -- though that doesn't explain why the sans-serif 
font is working.
Do you have any customizations related to fonts in your matplotlibrc file?
Mike
-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA
From: Michael D. <md...@st...> - 2010年10月04日 13:33:39
You can set the rcParam "ps.useafm" to True, which will use the built-in 
Postscript fonts (and not embed any in the file), or set "ps.fonttype" 
to "42" which will embed the complete Truetype font in the file.
Mike
On 10/02/2010 01:55 PM, Ed Lazarus wrote:
> All,
>
> I am wondering if anyone knows of a working example that yields
> a postscript figure editable in Adobe Illustrator; that is, the 
> characters are editable as characters.
> I have only been able to get drawn fonts and would love to have a test 
> case that is known to work.
>
> My environment is:
>> python
> Python 2.6.6 (r266:84292, Sep 11 2010, 15:25:14)
> [GCC 4.2.1 (Apple Inc. build 5659)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import matplotlib
>>>> matplotlib.__version__
> '1.0.0'
>>>> matplotlib.__file__
> '/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/matplotlib/__init__.pyc'
>>>>
> my rc file is:
> backend : TkAgg # the default backend
> interactive : True
> ps.usedistiller : xpdf
>
> I can produce postscript fonts outside python, say in IDL.
> I can produce postscript fonts in python using the psg package, but 
> not matplotlib.
> In all the examples at http://matplotlib.sourceforge.net/ I did not 
> find anything that
> explicitly addresses this issue.
>
> Thanks to anyone who answers with a test case.
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA
From: Michael D. <md...@st...> - 2010年10月04日 13:22:17
On 10/02/2010 01:39 PM, Jouni K. Seppänen wrote:
> Benjamin Root<ben...@ou...> writes:
>
> 
>> And yet, we still allow for saving to jpegs.
>> 
> Wow, I didn't know. Last time I tried that I got a traceback, and
> assumed that it was not supported exactly because jpeg is a nonsensical
> format for most graphs.
>
> I just tried again, and got "TypeError: 'int' object is unsubscriptable"
> from PIL/JpegImagePlugin.pyc in _save(im, fp, filename). I suppose this
> doesn't get much testing.
> 
Aside from the question of whether we "should" support JPEGs, etc., that 
code path should work (and in fact it does on my machine). What version 
of PIL do you have installed, and can you provide the full traceback 
here? I'd like to get to the bottom of this bug, even if it's an 
infrequently used feature.
Mike
-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA
From: Matthieu B. <mat...@gm...> - 2010年10月04日 12:44:54
Hello,
I ahve several installation of matplotlib on several computers with
different OS but the same HOME directory.
Matplotlib caches a lot of stuff in ~/.matplotlib, like fonts, but
they are not located in the same folder in different computers I use.
The issue is that the cache makes matplotlib raise an exception at
import time. Would it be possible not to use the cache if the fonts
mentioned int he cache are not available?
Matthieu
-- 
Information System Engineer, Ph.D.
Blog: http://matt.eifelle.com
LinkedIn: http://www.linkedin.com/in/matthieubrucher
From: Daπid <dav...@gm...> - 2010年10月04日 10:15:59
On Mon, Oct 4, 2010 at 11:36 AM, nickj <nic...@gm...> wrote:
> To better illustrate my problem, here is a screenshot with added red lines
> pointing to the odd slicing I get around the
> contours: http://www.bigoceans.com/slices.png
A low-tech option is to plot first all the oceans in light color, then
overplot the next color for all values (corresponding to that one an
higher) and so on.
For your performance issues, make sure you are not displaying the
image, but saving it directly to disk.
From: nickj <nic...@gm...> - 2010年10月04日 09:36:20
Hello all,
I'm playing with Matplotlib & Basemap for the first time, and attempting to
render data from the NOAA GFS models. With joy I finally got something on
screen, however I was wondering what I might be able to do, to better
improve the contour rendering of the final map. To better illustrate my
problem, here is a screenshot with added red lines pointing to the odd
slicing I get around the contours: http://www.bigoceans.com/slices.png
Is there any way to rectify that?
Also, part of my project is to output massively high resolution images of
this work, which I'll be using to display in a number of mediums which are
of particular aesthetic importance (I'm not a scientist, I'm producing
something more in the realm of infographics). I decided perhaps the best
method to achieve this is as a PDF/Vector output, which I could generate
bitmaps at a later date at any resolution I choose to render the PDF as
(upwards of 8000pixels). Would anyone be able to best recommend how I can
achieve the highest possible contouring, country borders and other things
related to detail? I have attempted to use the resolution=full keyword,
however my computer balked and failed to respond after five minutes. What is
this keyword actually doing? What can I do to get the greatest resolution of
coastline & map representation?
Thanks so much, Nick
From: Oren G. <og...@gm...> - 2010年10月04日 09:18:31
Hi,
I'm quite new to python and matplotlib so please forgive me if this quite
basic.
I need to annotate a distance on a image by a two arrowed bar. I tried using
arrowprops with arrowstyle = '<->' and connectionstyle='bar' but I could
find how to have the text above the bar and not at the edge of the bar.
Could someone drop clue?
Thanks,
OrenG
From: Eric F. <ef...@ha...> - 2010年10月03日 21:20:48
On 09/30/2010 08:28 AM, Joey Richards wrote:
> When I use the errorbar() routine to plot data, unless I set hold=True as a kwarg (or set it globally), the data are plotted without the errorbars. I believe it is because the routine first plots the error bars, then overplots the data points and for some reason the routine is clearing the axis in between these steps.
Fixed in 8724.
Eric
7 messages has been excluded from this view by a project administrator.

Showing results of 428

<< < 1 .. 14 15 16 17 18 > >> (Page 16 of 18)
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 によって変換されたページ (->オリジナル) /