matplotlib-users Mailing List for matplotlib (Page 7)

I am trying to prepare a plot on the UK national grid. This is a =
transverse mercator projection centred on the UK with a false origin =
offset from the projection origin (lat_0, lon_0).
The Basemap coordinate system origin (0 Easting and Northing) always =
seems to be set in the lower-left corner of the plot. The plot I need =
includes data either side of the origin so I need the origin within the =
plot area.
Is there a general way of setting the origin somewhere other than the =
lower-left corner?
I can either get basemap to plot the correct data region, in which case =
the origin is in the wrong place or I can fool Basemap by adjusting the =
axes bounds later. However, if I do this some of the coastline isn't =
plotted because Basemap decides it isn't on the map.
Cheers,
Stephen.

sidimok wrote:
>>> I would venture a guess that the problem is how to update the plot.
There are issues with calling Show() more than once - you may be able to 
set the interactive mode and get it to work.
the other option is to write a very simple app with a GUI toolkit -- see 
the embedding in ** examples.
If you want to do wxPython, you can use wxmpl to wrap MPL, and building 
a little app with wxTimer and a stop button would be really easy.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

>> I would venture a guess that the problem is how to update the plot.
That's it!
-- 
View this message in context: http://www.nabble.com/Update-and-replot-data-at-a-regular-time-rate-tf4600152.html#a13141806
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Oct 10, 2007, at 12:53 PM, massimo sandal wrote:
> sidimok ha scritto:
>> I would write down an MPL script that loads a block data, 
>> generated on the
>> fly (in a file) by another computing program, at a regular time 
>> rate, let's
>> say every 30". The script may have an "exit button" to stop it, 
>> and it might
>> proceed this way:
>> 1. time = time_old
>> 2. Load the "data" from lines 0 to -1(EOF)
>> 3. Save "data" length: N = len(data)
>> 4. plot
>> 5. After time_new-time_old = time_step
>> 5a. load "data_tmp" from lines N to -1
>> 5b. extend "data" with "data_tmp"
>> 5c. plot
>> 5d. Go back to step 5, or press "Stop" button
>> Does anyone have an idea how to encode this purpose?
>
> I don't really understand what the problem is. If you don't you 
> know how
> to wait a definite time between loading the file, have a look at the
> time module:
>
> http://docs.python.org/lib/module-time.html
>
> especially time.sleep()
>
> m.
I would venture a guess that the problem is how to update the plot.
I have not investigated this problem, but I have a hard time figuring
out how matplotlib deals with updating plots after plot.show() has
been called to plot to the screen the first time.
Cheers
 Tommy 

sidimok ha scritto:
> I would write down an MPL script that loads a block data, generated on the
> fly (in a file) by another computing program, at a regular time rate, let's
> say every 30". The script may have an "exit button" to stop it, and it might
> proceed this way:
> 
> 1. time = time_old
> 2. Load the "data" from lines 0 to -1(EOF)
> 3. Save "data" length: N = len(data)
> 4. plot
> 5. After time_new-time_old = time_step
> 5a. load "data_tmp" from lines N to -1
> 5b. extend "data" with "data_tmp"
> 5c. plot
> 5d. Go back to step 5, or press "Stop" button
> 
> Does anyone have an idea how to encode this purpose?
I don't really understand what the problem is. If you don't you know how
to wait a definite time between loading the file, have a look at the
time module:
http://docs.python.org/lib/module-time.html
especially time.sleep()
m.
-- 
Massimo Sandal
University of Bologna
Department of Biochemistry "G.Moruzzi"
snail mail:
Via Irnerio 48, 40126 Bologna, Italy
email:
mas...@un...
tel: +39-051-2094388
fax: +39-051-2094387

Hi everyone!
I would write down an MPL script that loads a block data, generated on the
fly (in a file) by another computing program, at a regular time rate, let's
say every 30". The script may have an "exit button" to stop it, and it might
proceed this way:
1. time = time_old
2. Load the "data" from lines 0 to -1(EOF)
3. Save "data" length: N = len(data)
4. plot
5. After time_new-time_old = time_step
 5a. load "data_tmp" from lines N to -1
 5b. extend "data" with "data_tmp"
 5c. plot
 5d. Go back to step 5, or press "Stop" button
Does anyone have an idea how to encode this purpose?
Thanks.
-- 
View this message in context: http://www.nabble.com/Update-and-replot-data-at-a-regular-time-rate-tf4600152.html#a13133808
Sent from the matplotlib - users mailing list archive at Nabble.com.

Great! Glad to know I wasn't going crazy ;)
Cheers,
Mike
Wayne E. Harlan wrote:
> By the time I did the update it was at 3931 but it works just fine. I 
> inserted the 6"x8" picture into swriter and it shows up at 6"x8". 
> Thank you very much !
> 
> Wayne
> 
> Michael Droettboom wrote:
>> Wayne E. Harlan wrote:
>>> Michael:
>>>
>>> Both r3927 and r3929 resulted in the smaller png file that's just 
>>> transparent background.
>>
>> The point of interest is r3926, before this change. r3927 and r3929 
>> are identical on the trunk.
>>
>> It turns out there was a peculiarity with how image files are saved in 
>> the GtkAgg backend that was triggering this bug. That should now be 
>> fixed in r3930. Please try that and let me know how that works for you.
>>
>>> It's roughly 20% of the size of the file I get with the latest 
>>> release, 0.90.1, which opens fine (but has the wrong dpi). That 
>>> tells me that on my system, some stuff just isn't getting written to 
>>> the file. I have attached my matplotlibrc and will read the docs to 
>>> see how to save a raw image and attach that, too. I don't have 
>>> ImageMagick, but can download and compile it later today. I tried a 
>>> 300 dpi jpg with r3929 and the image saves OK but has the wrong dpi 
>>> (72). The .raw image is also attached. It was over 17 MB so I 
>>> bzipped it. I'm surprised it ended up at 700 bytes !
>>
>> That raw file is fully white and transparent also.
>>
>> Hope that helps,
>> Mike
>>
>>> Wayne
>>>
>>> Michael Droettboom wrote:
>>>> Unfortunately, I'm not able to reproduce this here with the .py you 
>>>> attached. Both SVN r3926 (before the PNG resolution change) and SVN 
>>>> r3927 (after the PNG resolution change) work for me. Are you 
>>>> comparing those two SVN revisions, or SVN vs. 0.90.1?
>>>>
>>>> I can confirm that the PNG you attached is all white and fully 
>>>> transparent.
>>>>
>>>> Just for information, my machine (RHEL4) has libpng 1.2.7.
>>>>
>>>> Can you send a copy of your matplotlibrc? Also, can you save out a 
>>>> .raw image? (If you rename it to foo.rgba, you can display these 
>>>> images with the ImageMagick command "display -size 1800x1200 -depth 
>>>> 8 foo.rgba") That would help determine whether the problem is in the 
>>>> PNG-writing code or something higher up.
>>>>
>>>> Cheers,
>>>> Mike
>>>>
>>>> Wayne E. Harlan wrote:
>>>>> Michael:
>>>>>
>>>>> I tried a complete checkout for comparison (3929). In the 
>>>>> meantime, my libpng is 1.2.18 (installed from source as is 
>>>>> everything - this is an LFS/BLFS system.) Yes, the plot was 
>>>>> working before the change and I can send you some png's from that 
>>>>> if you need to see them, or I can backtrack to 0.90.1 and repeat 
>>>>> this. Please bear in mind that the plot displays (and always has) 
>>>>> quite correctly on screen - it's just the saved file that consists 
>>>>> of just background. I have attached the script, the resulting png 
>>>>> and a saved screenshot from the Gimp. Attachments are gzipped.
>>>>>
>>>>> Wayne
>>>>>
>>>>> Michael Droettboom wrote:
>>>>>> Hmmm. I'm very surprised that this change could cause that. All 
>>>>>> it does is add an additional metadata chunk to the PNG file, which 
>>>>>> shouldn't have any affect on the image data itself. 
>>>>>> simple_plot.py works fine for me in GIMP 2.0.5 both before and 
>>>>>> after this change. Can you verify that this plot was working 
>>>>>> before the change to save the resolution in the PNG file? If so, 
>>>>>> can you send me the source for your plot and the PNG file? Also, 
>>>>>> what version of libpng are you using? (pkg-config --version libpng 
>>>>>> should display this on most recent Linux distros).
>>>>>> 
>>>>
>>
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Adam Mercer wrote:
> On 09/10/2007, Jeff Whitaker <js...@fa...> wrote:
>
> 
>> Adam: If you can convert your coordinates into latitudes and
>> longitudes, then you can plot the data with the basemap tookit on your
>> choice of map projection (see
>> http://www.scipy.org/Cookbook/Matplotlib/Maps for an example).
>> 
>
> Following that example I'm running into a few problems, this is the code I have:
>
> map = Basemap(projection='ortho',lat_0=50,lon_0=-100,resolution='l',area_thresh=1000.)
> map.drawmeridians(pylab.arange(0,360,30))
> map.drawparallels(pylab.arange(-90,90,30))
> map.contour(lat, lon, values)
>
> where lat is an array of the latitude, lon the corresponding latitude
> and values the value of the quantity I want to plot, this results in
> the error:
>
> Traceback (most recent call last):
> File "./plot_skymap.py", line 54, in ?
> map.contour(lat, lon, values)
> File "/opt/local/lib/python2.4/site-packages/matplotlib/toolkits/basemap/basemap.py",
> line 2484, in contour
> xx = x[x.shape[0]/2,:]
> IndexError: too many indices
>
> Can anyone give me any pointers, on what the problem is here?
>
> Cheers
>
> Adam
> 
Adam: If lat and lon are 2D arrays containing the lats and lons of the 
grid in degrees, you first need to convert to map projection coordinates 
using the map instance:
x,y = map(lons, lats)
(if lons and lats are 1D, you can use pylab.meshgrid to make them 2D first)
Then you pass contour the x, y values
map.contour(x,y,values)
For filled contours use contourf.
Are you sure you want an orthographic projection? I thought sky maps 
used a stereographic projection 
(http://www.progonos.com/furuti/MapProj/Normal/ProjAppl/projAppl.html).
-Jeff
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449
325 Broadway Boulder, CO, USA 80305-3328

On Tuesday 09 October 2007 20:08:29 Adam Mercer wrote:
> On 09/10/2007, Jeff Whitaker <js...@fa...> wrote:
> > Adam: If you can convert your coordinates into latitudes and
> > longitudes, then you can plot the data with the basemap tookit on your
> > choice of map projection (see
> > http://www.scipy.org/Cookbook/Matplotlib/Maps for an example).
>
> Following that example I'm running into a few problems, this is the code I
> have:
Gonna assume that values is a 1D array, right ? I'm pretty sure that you need 
a 2D array for contours to work.
http://www.scipy.org/Cookbook/Matplotlib/Gridding_irregularly_spaced_data

On 09/10/2007, Jeff Whitaker <js...@fa...> wrote:
> Adam: If you can convert your coordinates into latitudes and
> longitudes, then you can plot the data with the basemap tookit on your
> choice of map projection (see
> http://www.scipy.org/Cookbook/Matplotlib/Maps for an example).
Following that example I'm running into a few problems, this is the code I have:
map = Basemap(projection='ortho',lat_0=50,lon_0=-100,resolution='l',area_thresh=1000.)
map.drawmeridians(pylab.arange(0,360,30))
map.drawparallels(pylab.arange(-90,90,30))
map.contour(lat, lon, values)
where lat is an array of the latitude, lon the corresponding latitude
and values the value of the quantity I want to plot, this results in
the error:
Traceback (most recent call last):
 File "./plot_skymap.py", line 54, in ?
 map.contour(lat, lon, values)
 File "/opt/local/lib/python2.4/site-packages/matplotlib/toolkits/basemap/basemap.py",
line 2484, in contour
 xx = x[x.shape[0]/2,:]
IndexError: too many indices
Can anyone give me any pointers, on what the problem is here?
Cheers
Adam

On 09/10/2007, Jeff Whitaker <js...@fa...> wrote:
> Adam: If you can convert your coordinates into latitudes and
> longitudes, then you can plot the data with the basemap tookit on your
> choice of map projection (see
> http://www.scipy.org/Cookbook/Matplotlib/Maps for an example).
Thats just what I'm after. Thanks a lot!
Cheers
Adam

Adam Mercer wrote:
> Hi
>
> I have some skymap data, i.e. theta, phi and some intensity that I
> would like to plot on the surface of a sphere, does matplotlib support
> plotting on the surface of a sphere? I've looked through the examples
> and can't seem to find anything.
>
> Any help would be greatly appreciated.
>
> Cheers
>
> Adam
>
> 
Adam: If you can convert your coordinates into latitudes and 
longitudes, then you can plot the data with the basemap tookit on your 
choice of map projection (see 
http://www.scipy.org/Cookbook/Matplotlib/Maps for an example).
-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-124
Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg

Hi
I have some skymap data, i.e. theta, phi and some intensity that I
would like to plot on the surface of a sphere, does matplotlib support
plotting on the surface of a sphere? I've looked through the examples
and can't seem to find anything.
Any help would be greatly appreciated.
Cheers
Adam

> Hi! I have some code importing MPL and wxmpl; presently, I have 
> version 0.90.1 of the former installed and 1.2.8 of the latter. I 
> hadn't run this code in a while; when I last did, in the late spring 
> sometime, it worked fine. Now, when I do (from the command line), a 
> call in it to <class-derived-from-wxmpl.PlotPanel>.Axes.clear() 
> results in an error seq. ending in AttributeError: 
> VectorLineCollection instance has no attribute 'get_xdata'. One 
> "catch": the "old" version still exists as a py2app-ed stand-alone; I 
> tried it and sure enough, it still works fine. By searching its Mac 
> App file tree, I was able to determine that this old py2app-ed version 
> is using version 0.90.0 of MPL; unfortunately, it (appears to be) 
> using a compiled version of wxmpl, so I don't know how to determine 
> what version of that its using. Did the update of MPL from 0.90.0 to 
> 0.90.1 change anything that might result in this error; has there been 
> a change in wxmpl which might result in this error? (Between then and 
> now, I switched to a new Mac and installed everything from scratch, so 
> it's very likely that my present version of wxmpl is different from 
> the one I had installed when I created the py2app.) Any other ideas? 
> (I'm at a total loss.) Thanks!
>
> DG
> -- 
> ERD/ORR/NOS/NOAA 
> <http://response.restoration.noaa.gov/emergencyresponse/>
Additional info: when I'm in the directory in which wxmpl.pyc resides 
inside the py2app bundle, run Python and import wxmpl, I get:
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
 File "wxmpl.pyc", line 18, in <module>
 (
 File "wx/__init__.pyc", line 45, in <module>
 File "wx/_core.pyc", line 4, in <module>
 File "wx/_core_.pyc", line 18, in <module>
 File "wx/_core_.pyc", line 15, in __load
 ImportError: 
'/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/lib-dynload/wx/_core_.so' 
not found
(Note that the application package from which I got this error is the 
version of the program that works!)
Following a suggestion, I copied this wxmpl.pyc to a place outside the 
application package, ran python, and it imported fine. I checked its 
version number and it's 1.2.8, same as what I have installed presently 
(wxmpl.__file__ verified that the local version was imported, not my 
site-packages version).
I'm at more of a loss than ever...
DG
-- 
ERD/ORR/NOS/NOAA <http://response.restoration.noaa.gov/emergencyresponse/>

On 10/9/07, Michael Droettboom <md...@st...> wrote:
> I don't know of any way to side step this -- for various reasons, the
> backend must be known during pylab initialization. It might be possible
> with fairly significant refactoring... maybe someone has looked deeper
> into this than I have.
There is a "switch_backends" function in pylab that attempts to do a
post import switching. It works reasonably well, but is not
recommended for switching across threaded GUI backends (eg in
ipython), which is why it has mostly remained an experimental feature.
JDH

Chris wrote:
> Updating matplotlib with a new SVN build a couple days ago induced
> the following error:
> 
> RuntimeError: matplotlib.use() must be called *before* pylab
> or matplotlib.backends is imported for the first time.
> 
> This has not occurred before. Am I to understand that once pylab
> is imported, you cannot change backends? That seems strange. Is 
> there a way of side-stepping this?
This has long been the case, but only recently was an error added. (It 
was confusing to many who *thought* they were changing the backend, when 
in fact they weren't.)
I don't know of any way to side step this -- for various reasons, the 
backend must be known during pylab initialization. It might be possible 
with fairly significant refactoring... maybe someone has looked deeper 
into this than I have.
Cheers,
Mike
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Updating matplotlib with a new SVN build a couple days ago induced
the following error:
RuntimeError: matplotlib.use() must be called *before* pylab
or matplotlib.backends is imported for the first time.
This has not occurred before. Am I to understand that once pylab
is imported, you cannot change backends? That seems strange. Is 
there a way of side-stepping this?

Unfortunately, I'm not able to reproduce this here with the .py you 
attached. Both SVN r3926 (before the PNG resolution change) and SVN 
r3927 (after the PNG resolution change) work for me. Are you comparing 
those two SVN revisions, or SVN vs. 0.90.1?
I can confirm that the PNG you attached is all white and fully transparent.
Just for information, my machine (RHEL4) has libpng 1.2.7.
Can you send a copy of your matplotlibrc? Also, can you save out a .raw 
image? (If you rename it to foo.rgba, you can display these images with 
the ImageMagick command "display -size 1800x1200 -depth 8 foo.rgba") 
That would help determine whether the problem is in the PNG-writing code 
or something higher up.
Cheers,
Mike
Wayne E. Harlan wrote:
> Michael:
> 
> I tried a complete checkout for comparison (3929). In the meantime, my 
> libpng is 1.2.18 (installed from source as is everything - this is an 
> LFS/BLFS system.) Yes, the plot was working before the change and I can 
> send you some png's from that if you need to see them, or I can 
> backtrack to 0.90.1 and repeat this. Please bear in mind that the plot 
> displays (and always has) quite correctly on screen - it's just the 
> saved file that consists of just background. I have attached the 
> script, the resulting png and a saved screenshot from the Gimp. 
> Attachments are gzipped.
> 
> Wayne
> 
> Michael Droettboom wrote:
>> Hmmm. I'm very surprised that this change could cause that. All it 
>> does is add an additional metadata chunk to the PNG file, which 
>> shouldn't have any affect on the image data itself. simple_plot.py 
>> works fine for me in GIMP 2.0.5 both before and after this change. 
>> Can you verify that this plot was working before the change to save 
>> the resolution in the PNG file? If so, can you send me the source for 
>> your plot and the PNG file? Also, what version of libpng are you 
>> using? (pkg-config --version libpng should display this on most recent 
>> Linux distros).
>> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Michael:
I tried a complete checkout for comparison (3929). In the meantime, my 
libpng is 1.2.18 (installed from source as is everything - this is an 
LFS/BLFS system.) Yes, the plot was working before the change and I can 
send you some png's from that if you need to see them, or I can 
backtrack to 0.90.1 and repeat this. Please bear in mind that the plot 
displays (and always has) quite correctly on screen - it's just the 
saved file that consists of just background. I have attached the 
script, the resulting png and a saved screenshot from the Gimp. 
Attachments are gzipped.
Wayne
Michael Droettboom wrote:
> Hmmm. I'm very surprised that this change could cause that. All it 
> does is add an additional metadata chunk to the PNG file, which 
> shouldn't have any affect on the image data itself. simple_plot.py 
> works fine for me in GIMP 2.0.5 both before and after this change. Can 
> you verify that this plot was working before the change to save the 
> resolution in the PNG file? If so, can you send me the source for your 
> plot and the PNG file? Also, what version of libpng are you using? 
> (pkg-config --version libpng should display this on most recent Linux 
> distros).
> 

Hi! I have some code importing MPL and wxmpl; presently, I have version 
0.90.1 of the former installed and 1.2.8 of the latter. I hadn't run 
this code in a while; when I last did, in the late spring sometime, it 
worked fine. Now, when I do (from the command line), a call in it to 
<class-derived-from-wxmpl.PlotPanel>.Axes.clear() results in an error 
seq. ending in AttributeError: VectorLineCollection instance has no 
attribute 'get_xdata'. One "catch": the "old" version still exists as a 
py2app-ed stand-alone; I tried it and sure enough, it still works fine. 
By searching its Mac App file tree, I was able to determine that this 
old py2app-ed version is using version 0.90.0 of MPL; unfortunately, it 
(appears to be) using a compiled version of wxmpl, so I don't know how 
to determine what version of that its using. Did the update of MPL from 
0.90.0 to 0.90.1 change anything that might result in this error; has 
there been a change in wxmpl which might result in this error? (Between 
then and now, I switched to a new Mac and installed everything from 
scratch, so it's very likely that my present version of wxmpl is 
different from the one I had installed when I created the py2app.) Any 
other ideas? (I'm at a total loss.) Thanks!
DG
-- 
ERD/ORR/NOS/NOAA <http://response.restoration.noaa.gov/emergencyresponse/>

On 2007年10月08日, Michael Droettboom apparently wrote:
> If there are any particular things that are particularly 
> bad, please send an example plot that exercises it. 
I have noticed that scatter plots take a very long time to 
render. (Use say four subplots each with three hundred points.)
Cheers,
Alan Isaac

Alan G Isaac wrote:
> On 2007年10月08日, Michael Droettboom apparently wrote:
>> http://sourceforge.net/tracker/index.php?func=detail&aid=1738494&group_id=80706&atid=560720 
>> This patch applies cleanly against 0.90.1 
> 
> Yes, that fixes it.
> 
> Perhaps I should mention that the PDF rendering is very slow.
Yes, PDF is probably one of the slowest backends in matplotlib, mainly 
due to the inherent complexity of the file format, with all of its 
cross-references etc. If there are any particular things that are 
particularly bad, please send an example plot that exercises it.
Cheers,
Mike
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

On 2007年10月08日, Michael Droettboom apparently wrote:
> http://sourceforge.net/tracker/index.php?func=detail&aid=1738494&group_id=80706&atid=560720 
> This patch applies cleanly against 0.90.1 
Yes, that fixes it.
Perhaps I should mention that the PDF rendering is very slow.
Thanks!
Alan Isaac

Hello to all,
I have found a peculiar behavior of matplotlib function errorbar.
See the code below and execute it all in once.
What I get is that first image is ok.
Second one loses all errorbar vertical line.
I noticed that while i was generating some graphs with errorbar in a for cycle 
and i tried to plot also some dots over each one. 
import pylab as p
p.figure(1)
p.errorbar([1,2,3,4],[1,2,3,4],[4,2,5,3])
p.hold(True)
# here plot what you wants
p.hold(False)
p.savefig('test_1.png')
p.close()
p.figure(1)
p.errorbar([1,2,3,4],[1,2,3,4],[4,2,5,3])
p.hold(True)
# here plot what you wants
p.hold(False)
p.savefig('test_2.png')
p.close()
-- 
--
Emanuele Passera

This is a problem using matplotlib 0.90.1 with Python 2.5.
See here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1738494&group_id=80706&atid=560720
This patch applies cleanly against 0.90.1
Cheers,
Mike
Alan G Isaac wrote:
> I'm having troubles saving figures as PDF.
> Matplotlib version 0.90.1
> Simple example below.
> 
> Cheers,
> Alan Isaac
> 
> 
> Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 
> 32 bit (Intel)] on win32
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import pylab
>>>> fig = pylab.figure()
>>>> pylab.plot([1,2,3])
> [<matplotlib.lines.Line2D instance at 0x016FF828>]
>>>> fig.savefig('c:/temp/temp.pdf')
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "C:\Python25\Lib\site-packages\matplotlib\figure.py", line 759, in savefig
> self.canvas.print_figure(*args, **kwargs)
> File "C:\Python25\Lib\site-packages\matplotlib\backends\backend_tkagg.py", line 188, in print_figu
> re
> **kwargs)
> File "C:\Python25\Lib\site-packages\matplotlib\backends\backend_agg.py", line 497, in print_figure
> 
> printfunc(filename, dpi, facecolor, edgecolor, orientation, **kwargs)
> File "C:\Python25\Lib\site-packages\matplotlib\backends\backend_pdf.py", line 1395, in print_figur
> e
> file.close()
> File "C:\Python25\Lib\site-packages\matplotlib\backends\backend_pdf.py", line 401, in close
> self.writeFonts()
> File "C:\Python25\Lib\site-packages\matplotlib\backends\backend_pdf.py", line 456, in writeFonts
> fontdictObject = self.embedTTF(filename)
> File "C:\Python25\Lib\site-packages\matplotlib\backends\backend_pdf.py", line 508, in embedTTF
> widths = [ get_char_width(charcode) for charcode in range(firstchar, lastchar+1) ]
> File "C:\Python25\Lib\site-packages\matplotlib\backends\backend_pdf.py", line 505, in get_char_wid
> th
> unicode = cp1252.decoding_map[charcode] or 0
> AttributeError: 'module' object has no attribute 'decoding_map'
> 
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA