matplotlib-users Mailing List for matplotlib

On Tue, Sep 23, 2008 at 3:28 PM, C M <cmp...@gm...> wrote:
> I'm hoping to get help from matplotlib wxPython backend users...
>
> I'm struggling to get what is described in the subject line to work correctly.
> There was a sort of similar thread from 2006 here:
>
> http://www.mail-archive.com/mat...@li.../msg00945.html
>
> I want to pick a point on a plot and use the x,y of that point to
> place a wxPopupWindow
> right near that point on the graph. I am doing this in wxPython as an embedded
> graph). I have it working *somewhat* but there is still a major
> problem with it.
> I tried to base this off the wxPython demos wxPopupWindow code, but somehow
> it is not working right.
Warning: the following is based on MPL 0.90.1 (yeah, I know, but it
works. We have a branch that works with 0.98 but it hasn't been merge
back in. Your mileage may vary.)
Our popup code does:
(note that in the bit below, self is a subclassed object based on
FigureCanvasWxAgg)
mouseLocation = wx.GetMousePosition()
pos = self.ScreenToClient(mouseLocation)
height = self.figure.bbox.height()
x = pos.x
y = height - pos.y
(pickType, pickDetails) = self._pick(x,y) # NB: This is a custom pick
routine written before the new pick code
....
self.popup = ProbePopupWindow(self, wx.SIMPLE_BORDER,
series.getName(), mouseLocation)
where ProbePopupWindow is a subclass of wx.PopupWindow, and the
positioning bit in the __init__ is:
self.Position(mouseLocation, (10,10))
HTH,
Anthony.

I'm hoping to get help from matplotlib wxPython backend users...
I'm struggling to get what is described in the subject line to work correctly.
There was a sort of similar thread from 2006 here:
http://www.mail-archive.com/mat...@li.../msg00945.html
I want to pick a point on a plot and use the x,y of that point to
place a wxPopupWindow
right near that point on the graph. I am doing this in wxPython as an embedded
graph). I have it working *somewhat* but there is still a major
problem with it.
I tried to base this off the wxPython demos wxPopupWindow code, but somehow
it is not working right.
Before I post any code or if I can get a runnable sample going, does anyone
have a pointer to a simple solution? I can get x and y in pixel space on the
graph from event.mouseevent.x and event.mouseevent.y, but then when I try
to sort of add those to the position of the frame which contains the panel
(which contains the graph), I get some really weird behavior when I move that
frame to the left: the location of the popupwindow jumps to the far right side
of the screen.
Any help is appreciated--Thanks!

De Pauw Antoine wrote:
> Jeff,
>
> I still don't know how to either remove this artifact or fill my arrays with
> values to remove empty regions, and I'll make a last attempt to resolve it
>
> I uploaded a data file here: http://scqp.ulb.ac.be/20080821.b56
>
> The actual code snippet is here:
> http://snipplr.com/view/8307/map-plotting-python-code-temporary/
>
> I hope you'll be able to reproduce it, I set the cmap to winter for you to
> see the gap... setting it to hot will make the grayish border visible in
> high resolution by zooming it... I think the border (not the empty zone)
> could be an artifact with the hot colormap
>
>
> Antoine De Pauw
> Collaborateur de recherches, Informatique - Research collaborator, IT
> Laboratoire de chimie quantique et photophysique - Quantum chemistry and
> photophysics laboratory
> Université Libre de Bruxelles - ULB
>
> 
Antoine: Here is a version that just plots the pixels directly, without 
interpolating to a grid. I personally like this better, since you can 
easily see where you actually have data.
HTH,
-Jeff
from mpl_toolkits.basemap import Basemap
import matplotlib.pyplot as plt
import matplotlib.mlab as mlab
import numpy as np
import os
fileName = '20080821.b56'
titre='SO2'
legende='Delta Brightness Temperature (K)'
nbreligne=long(os.stat(fileName)[6])/(8*int(fileName[-2:]))
rawfile=np.fromfile(open(fileName,'rb'),'<d',-1)
Lat=rawfile[0:nbreligne]
Lon=rawfile[nbreligne:nbreligne*2]
Val=rawfile[nbreligne*21:nbreligne*22]
map=Basemap(projection='mill',llcrnrlat=-90,urcrnrlat=90,\
 urcrnrlon=180,llcrnrlon=-180,resolution='l')
x, y = map(Lon, Lat)
plt.scatter(x,y,s=25,c=Val,marker='s',edgecolor="None",cmap=plt.cm.winter,vmin=-5,vmax=-1.2, 
alpha=0.5)
cb=plt.colorbar(shrink=0.6)
cb.ax.set_ylabel(legende,fontsize=11)
for t in cb.ax.get_yticklabels():
 t.set_fontsize(7)
meridians = np.arange(-180,180,60)
parallels = np.arange(-90,90,30)
map.drawparallels(parallels,labels=[1,0,0,0],fontsize=7,linewidth=0.25)
map.drawmeridians(meridians,labels=[0,0,0,1],fontsize=7,linewidth=0.25)
map.drawcoastlines(0.25,antialiased=1)
plt.title(titre)
plt.show()
> -----Original Message-----
> From: Jeff Whitaker [mailto:js...@fa...] 
> Sent: lundi 22 septembre 2008 13:59
> To: De Pauw Antoine
> Cc: 'John Hunter'; 'Matplotlib Users'
> Subject: Re: [Matplotlib-users] Information request
>
> De Pauw Antoine wrote:
> 
>> Jeff,
>>
>> I included here a figure where you'll see the border problem for imshow in
>> my case
>>
>> http://img217.imageshack.us/img217/5240/testfigzp3.png
>>
>> The border wraps at -180 and 180 to form the white line
>>
>> PS: it is atmospheric ice and not SO2, I just omitted to change the title
>> 
> ^^
> 
>> Antoine De Pauw
>> Collaborateur de recherches, Informatique - Research collaborator, IT
>> Laboratoire de chimie quantique et photophysique - Quantum chemistry and
>> photophysics laboratory
>> Université Libre de Bruxelles - ULB
>> 
>> 
>
> Antoine: I hate to keep repeating myself - but we can't do much if you 
> don't provide a self-contained script, that I can run, which reproduces 
> the problem. My guess is that the line along the dateline, and the 
> point at the South Pole are missing values (which griddata set to 
> missing because they are outside the extent of the data) - but that's 
> just a guess until I can reproduce it.
>
> -Jeff
> 
>> -----Original Message-----
>> From: Antoine De Pauw [mailto:and...@ul...] 
>> Sent: jeudi 18 septembre 2008 17:23
>> To: Jeff Whitaker; and...@ul...
>> Cc: 'John Hunter'; 'Matplotlib Users'
>> Subject: re:Re: [Matplotlib-users] Information request
>>
>> Jeff,
>>
>> No the example doesn't show that line
>>
>> If I reduce the amount of data, the border will be on every side of the
>> 
> plot
> 
>> I'll show you an orthographic plot with no maskinf tomorrow and you will
>> 
> see
> 
>> the problem easily, it wraps in a white line along the 0° meridian and a
>> white circle in the pole
>>
>> I think it's the imshow layer that is not totally transparent on the map
>> background.. I tried every trick I could for example to put some
>> 
> zero-valued
> 
>> points on each corner to make imshow interpolate correctly the sides, but
>> that doesn't make any difference
>>
>> 
>> 
>>> De Pauw Antoine wrote:
>>> 
>>> 
>>>> Jeff,
>>>>
>>>> Yes they disappear, and they fluctuate with the interpolation method
>>>> 
> used
> 
>>>> For example, nearest interpolation don't show the line
>>>>
>>>> Also, if I reduce the grid resolution, the line is thicker, and if I use
>>>> 
>>>> 
>> a
>> 
>> 
>>>> masked array to get rid of undesired values, the border shows really
>>>> strongly
>>>>
>>>> Here's an example everyone will see:
>>>>
>>>> http://img225.imageshack.us/img225/2671/testfigep2.png
>>>>
>>>> (everything except the clouds is noise)
>>>>
>>>> Antoine De Pauw
>>>> Collaborateur de recherches, Informatique - Research collaborator, IT
>>>> Laboratoire de chimie quantique et photophysique - Quantum chemistry and
>>>> photophysics laboratory
>>>> Université Libre de Bruxelles - ULB
>>>> 
>>>> 
>>>> 
>>> Antoine: Sorry to seem dense, but I don't see anything wrong with that 
>>> plot. I see a white border along the north and south pole, but I 
>>> intrepret that to be missing values. However, my eyes are notoriously 
>>> bad. I'd like to be to run a script that generates the artifacts 
>>> myself, so I can zoom in and see the problem myself. Does the 
>>> griddata_demo.py script show the same problem for you?
>>>
>>> -Jeff
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: Jeff Whitaker [mailto:js...@fa...] 
>>>> Sent: mercredi 17 septembre 2008 19:05
>>>> To: John Hunter
>>>> Cc: De Pauw Antoine; Matplotlib Users
>>>> Subject: Re: [Matplotlib-users] Information request
>>>>
>>>> John Hunter wrote:
>>>> 
>>>> 
>>>> 
>>>>> On Wed, Sep 17, 2008 at 11:54 AM, John Hunter <jd...@gm...>
>>>>> 
> wrote:
> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> Attached is a screenshot (zoom.png) from the gimp, zoomed in near the
>>>>>> axes border. The black horizontal line is the top axes border, the
>>>>>> horizontal grey line is the artifact, the vertical dashed line is a
>>>>>> grid line. I don't know if this offers a clue, but if you look at a
>>>>>> zoom in the upper right corner, the grey line seems to break up and
>>>>>> curve down and to the right (corner.png)
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> Sorry, screwed up corner.png (I attached the original and not the
>>>>> screenshot). The correct screenshot is attached
>>>>> 
>>>>>
>>>>>
>>>>> 
>>>>> 
>>>>> 
>>>> John: OK, now I finally see it. Antoine: Do these artifacts 
>>>> disappear if you comment out the imshow call?
>>>>
>>>> -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
>>>
>>>
>>>
>>> 
>>> 
>> 
>> 
>
>
> 
-- 
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

It looks like those examples suspend operation while waiting for a click, after going to mainloop().
On a related note, after I use pylab.plot() to draw the screen, the toolbar is inaccessible unless I also use show(), which then halts the program until I close the window. 
 

De Pauw Antoine wrote:
> Jeff,
>
> I still don't know how to either remove this artifact or fill my arrays with
> values to remove empty regions, and I'll make a last attempt to resolve it
>
> I uploaded a data file here: http://scqp.ulb.ac.be/20080821.b56
>
> The actual code snippet is here:
> http://snipplr.com/view/8307/map-plotting-python-code-temporary/
>
> I hope you'll be able to reproduce it, I set the cmap to winter for you to
> see the gap... setting it to hot will make the grayish border visible in
> high resolution by zooming it... I think the border (not the empty zone)
> could be an artifact with the hot colormap
>
>
> Antoine De Pauw
> Collaborateur de recherches, Informatique - Research collaborator, IT
> Laboratoire de chimie quantique et photophysique - Quantum chemistry and
> photophysics laboratory
> Université Libre de Bruxelles - ULB
>
>
> 
Antoine: As I suspected, that gap around the edges of the plot is a 
consequence of the gridding procedure. griddata doesn't do 
extrapolation, so there are missing values on the grid outside the 
convex hull of the input observations. You can either just live with 
it, or set the plotting region so that it fits entirely within the 
convex hull of the data. This is what I've done in the modified version 
of your script below. I've also eliminated the transform_scalar call by 
gridding directly on the projection grid (instead of gridding to a 
lat/lon grid, then interpolating to the projection grid). Hope this helps.
-Jeff
from mpl_toolkits.basemap import Basemap
import matplotlib.pyplot as plt
import matplotlib.mlab as mlab
import numpy as np
import os
fileName = '20080821.b56'
nx = 360; ny = 180
titre='SO2'
legende='Delta Brightness Temperature (K)'
nbreligne=long(os.stat(fileName)[6])/(8*int(fileName[-2:]))
rawfile=np.fromfile(open(fileName,'rb'),'<d',-1)
Lat=rawfile[0:nbreligne]
Lon=rawfile[nbreligne:nbreligne*2]
Val=rawfile[nbreligne*21:nbreligne*22]
map=Basemap(projection='mill',llcrnrlat=-89,urcrnrlat=89,\
 urcrnrlon=179,llcrnrlon=-179,resolution='l')
xi=np.linspace(map.xmin,map.xmax,nx)
yi=np.linspace(map.ymin,map.ymax,ny)
x, y = map(Lon, Lat)
zi=mlab.griddata(x,y,Val,xi,yi)
map.imshow(zi,plt.cm.winter,vmin=-5,vmax=-1.2)
cb=plt.colorbar(shrink=0.6)
cb.ax.set_ylabel(legende,fontsize=11)
for t in cb.ax.get_yticklabels():
 t.set_fontsize(7)
meridians = np.arange(-180,180,60)
parallels = np.arange(-90,90,30)
map.drawparallels(parallels,labels=[1,0,0,0],fontsize=7,linewidth=0.25)
map.drawmeridians(meridians,labels=[0,0,0,1],fontsize=7,linewidth=0.25)
map.drawcoastlines(0.25,antialiased=1)
plt.title(titre)
plt.show()
> -----Original Message-----
> From: Jeff Whitaker [mailto:js...@fa...] 
> Sent: lundi 22 septembre 2008 13:59
> To: De Pauw Antoine
> Cc: 'John Hunter'; 'Matplotlib Users'
> Subject: Re: [Matplotlib-users] Information request
>
> De Pauw Antoine wrote:
> 
>> Jeff,
>>
>> I included here a figure where you'll see the border problem for imshow in
>> my case
>>
>> http://img217.imageshack.us/img217/5240/testfigzp3.png
>>
>> The border wraps at -180 and 180 to form the white line
>>
>> PS: it is atmospheric ice and not SO2, I just omitted to change the title
>> 
> ^^
> 
>> Antoine De Pauw
>> Collaborateur de recherches, Informatique - Research collaborator, IT
>> Laboratoire de chimie quantique et photophysique - Quantum chemistry and
>> photophysics laboratory
>> Université Libre de Bruxelles - ULB
>> 
>> 
>
> Antoine: I hate to keep repeating myself - but we can't do much if you 
> don't provide a self-contained script, that I can run, which reproduces 
> the problem. My guess is that the line along the dateline, and the 
> point at the South Pole are missing values (which griddata set to 
> missing because they are outside the extent of the data) - but that's 
> just a guess until I can reproduce it.
>
> -Jeff
> 
>> -----Original Message-----
>> From: Antoine De Pauw [mailto:and...@ul...] 
>> Sent: jeudi 18 septembre 2008 17:23
>> To: Jeff Whitaker; and...@ul...
>> Cc: 'John Hunter'; 'Matplotlib Users'
>> Subject: re:Re: [Matplotlib-users] Information request
>>
>> Jeff,
>>
>> No the example doesn't show that line
>>
>> If I reduce the amount of data, the border will be on every side of the
>> 
> plot
> 
>> I'll show you an orthographic plot with no maskinf tomorrow and you will
>> 
> see
> 
>> the problem easily, it wraps in a white line along the 0° meridian and a
>> white circle in the pole
>>
>> I think it's the imshow layer that is not totally transparent on the map
>> background.. I tried every trick I could for example to put some
>> 
> zero-valued
> 
>> points on each corner to make imshow interpolate correctly the sides, but
>> that doesn't make any difference
>>
>> 
>> 
>>> De Pauw Antoine wrote:
>>> 
>>> 
>>>> Jeff,
>>>>
>>>> Yes they disappear, and they fluctuate with the interpolation method
>>>> 
> used
> 
>>>> For example, nearest interpolation don't show the line
>>>>
>>>> Also, if I reduce the grid resolution, the line is thicker, and if I use
>>>> 
>>>> 
>> a
>> 
>> 
>>>> masked array to get rid of undesired values, the border shows really
>>>> strongly
>>>>
>>>> Here's an example everyone will see:
>>>>
>>>> http://img225.imageshack.us/img225/2671/testfigep2.png
>>>>
>>>> (everything except the clouds is noise)
>>>>
>>>> Antoine De Pauw
>>>> Collaborateur de recherches, Informatique - Research collaborator, IT
>>>> Laboratoire de chimie quantique et photophysique - Quantum chemistry and
>>>> photophysics laboratory
>>>> Université Libre de Bruxelles - ULB
>>>> 
>>>> 
>>>> 
>>> Antoine: Sorry to seem dense, but I don't see anything wrong with that 
>>> plot. I see a white border along the north and south pole, but I 
>>> intrepret that to be missing values. However, my eyes are notoriously 
>>> bad. I'd like to be to run a script that generates the artifacts 
>>> myself, so I can zoom in and see the problem myself. Does the 
>>> griddata_demo.py script show the same problem for you?
>>>
>>> -Jeff
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: Jeff Whitaker [mailto:js...@fa...] 
>>>> Sent: mercredi 17 septembre 2008 19:05
>>>> To: John Hunter
>>>> Cc: De Pauw Antoine; Matplotlib Users
>>>> Subject: Re: [Matplotlib-users] Information request
>>>>
>>>> John Hunter wrote:
>>>> 
>>>> 
>>>> 
>>>>> On Wed, Sep 17, 2008 at 11:54 AM, John Hunter <jd...@gm...>
>>>>> 
> wrote:
> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> Attached is a screenshot (zoom.png) from the gimp, zoomed in near the
>>>>>> axes border. The black horizontal line is the top axes border, the
>>>>>> horizontal grey line is the artifact, the vertical dashed line is a
>>>>>> grid line. I don't know if this offers a clue, but if you look at a
>>>>>> zoom in the upper right corner, the grey line seems to break up and
>>>>>> curve down and to the right (corner.png)
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> Sorry, screwed up corner.png (I attached the original and not the
>>>>> screenshot). The correct screenshot is attached
>>>>> 
>>>>>
>>>>>
>>>>> 
>>>>> 
>>>>> 
>>>> John: OK, now I finally see it. Antoine: Do these artifacts 
>>>> disappear if you comment out the imshow call?
>>>>
>>>> -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
>>>
>>>
>>>
>>> 
>>> 
>> 
>> 
>
>
> 
-- 
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

I don't think my message made it to the mailing list... See below.
Charles
==========
The 2nd Law of Thermodynamics... If you think things are a mess now, JUST
WAIT!
---------- Forwarded message ----------
From: charles reid <cha...@gm...>
Date: Fri, Sep 19, 2008 at 5:46 PM
Subject: Re: [Matplotlib-users] installation
To: Robert Fenwick <rob...@ir...>
Cc: mat...@li...
The pre-installed version of python is NOT rubbish, it's used by the system
to do various tasks. If you delete it, it will likely mess things up. I
highly recommend you leave it alone. I would recommend you do a simple web
search, since there are a whole slew of guides to doing this. Try this one:
http://www.mtheory.co.uk/support/index.php?title=Installing_Python_-_iPython%2C_Numpy%2C_Scipy_and_Matplotlib_on_OS_X
There is a list of links at the bottom with at least 5 more guides to
installing "python for science" on Mac OS X 10.5 ("python for science" being
the suite of iPython, SciPy, NumPy, and matplotlib). Also try this handy
"SciPy Superpack" script:
http://macinscience.org/?page_id=6
It atuomatically downloads & installs the python for science programs from
the svn source (so you don't have to worry about updating, you just re-run
the script).
Good luck.
Charles
==========
The 2nd Law of Thermodynamics... If you think things are a mess now, JUST
WAIT!
On Fri, Sep 19, 2008 at 2:29 AM, Robert Fenwick <
rob...@ir...> wrote:
> Hi,
>
> I would really like to use matplot lib, however I am having big
> problems as I try to do this on OSX 10.5. if there is someone how
> could give a detailed explination of how to get rid of the
> preinstalled python that is apparently rubbish and then how to install
> a new python version that would really help me. I am completely lost
> in a world of eggs etc.
>
> Bryn
>
> P.S. here is my particular compilation problem. Is there a simple
> solution so that I can code my first graph today?
>
> salvatella02:Downloads rbf$ sudo easy_install
> matplotlib-0.98.3-py2.5-macosx-10.3.egg
> Password:
> Processing matplotlib-0.98.3-py2.5-macosx-10.3.egg
> removing
> '/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.3-py2.5-macosx-10.3.egg'
> (and everything under it)
> creating
> /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.3-py2.5-macosx-10.3.egg
> Extracting matplotlib-0.98.3-py2.5-macosx-10.3.egg to
>
> /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages
> Adding matplotlib 0.98.3 to easy-install.pth file
>
> Installed
> /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.3-py2.5-macosx-10.3.egg
> Processing dependencies for matplotlib==0.98.3
> Searching for matplotlib==0.98.3
> Reading http://pypi.python.org/simple/matplotlib/
> Reading http://matplotlib.sourceforge.net
> Reading
> https://sourceforge.net/project/showfiles.php?group_id=80706&package_id=278194
> Reading
> https://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474
> Reading
> http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474
> Reading http://sourceforge.net/project/showfiles.php?group_id=80706
> Best match: matplotlib 0.98.3
> Downloading
> http://downloads.sourceforge.net/matplotlib/matplotlib-0.98.3.tar.gz?modtime=1217773039&big_mirror=0
> Processing matplotlib-0.98.3.tar.gz
> Running matplotlib-0.98.3/setup.py -q bdist_egg --dist-dir
> /tmp/easy_install-JGl_1Z/matplotlib-0.98.3/egg-dist-tmp-T6PVvy
>
> ============================================================================
> BUILDING MATPLOTLIB
> matplotlib: 0.98.3
> python: 2.5.2 (r252:60911, Feb 22 2008, 07:57:53) [GCC
> 4.0.1 (Apple Computer, Inc. build 5363)]
> platform: darwin
>
> REQUIRED DEPENDENCIES
> numpy: 1.1.1
> freetype2: found, but unknown version (no pkg-config)
>
> OPTIONAL BACKEND DEPENDENCIES
> libpng: found, but unknown version (no pkg-config)
> Tkinter: Tkinter: 50704, Tk: 8.4, Tcl: 8.4
> wxPython: no
> * wxPython not found
> Gtk+: no
> * Building for Gtk+ requires pygtk; you must be able
> * to "import gtk" in your build/install environment
> Qt: no
> Qt4: no
> Cairo: no
>
> OPTIONAL DATE/TIMEZONE DEPENDENCIES
> datetime: present, version unknown
> dateutil: matplotlib will provide
> pytz: matplotlib will provide
>
> OPTIONAL USETEX DEPENDENCIES
> dvipng: 1.9
> ghostscript: 8.57
> latex: 3.141592
>
> EXPERIMENTAL CONFIG PACKAGE DEPENDENCIES
> configobj: matplotlib will provide
> enthought.traits: no
>
> [Edit setup.cfg to suppress the above messages]
>
> ============================================================================
> warning: no files found matching 'NUMARRAY_ISSUES'
> warning: no files found matching 'MANIFEST'
> warning: no files found matching 'matplotlibrc'
> warning: no files found matching 'makeswig.py'
> warning: no files found matching 'examples/data/*'
> warning: no files found matching 'lib/mpl_toolkits'
> warning: no files found matching '*' under directory 'examples'
> warning: no files found matching '*' under directory 'swig'
> gcc: unrecognized option '-no-cpp-precomp'
> cc1plus: error: unrecognized command line option "-arch"
> cc1plus: error: unrecognized command line option "-arch"
> cc1plus: warning: unrecognized command line option "-Wno-long-double"
> error: Setup script exited with error: command 'gcc' failed with exit
> status 1
> Exception exceptions.OSError: (2, 'No such file or directory',
> 'src/image.cpp') in <bound method CleanUpFile.__del__ of
> <setupext.CleanUpFile instance at 0x1bb48a0>> ignored
> Exception exceptions.OSError: (2, 'No such file or directory',
> 'src/path.cpp') in <bound method CleanUpFile.__del__ of
> <setupext.CleanUpFile instance at 0x1bb4080>> ignored
> Exception exceptions.OSError: (2, 'No such file or directory',
> 'src/backend_agg.cpp') in <bound method CleanUpFile.__del__ of
> <setupext.CleanUpFile instance at 0x1bb43c8>> ignored
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

No. Interestingly, I didn't get the same errors this morning as I did 
last night - I got build errors regarding ftbuild (or something like 
that). I had just installed Tcl/Tk from source, so perhaps the first 
time my shell hadn't figured out where they were (??). After I 
installed freetype-devel, the build errors went away. The Tk errors 
vanished on their own.
I don't know why I have so much trouble building and installing software...
Thanks,
Mike Hearne
John Hunter wrote:
> On Tue, Sep 23, 2008 at 10:28 AM, Michael Hearne <mh...@us...> wrote:
> 
>> I installed the freetype-devel libraries and this problem went away.
>>
>> 
>
> Any chance you also installed tk-devel or tcl-devel? I can't see how
> the addition of the freetype headers would fix a tk problem.
>
> JDH
> 
-- 
------------------------------------------------------
Michael Hearne
mh...@us...
(303) 273-8620
USGS National Earthquake Information Center
1711 Illinois St. Golden CO 80401
Senior Software Engineer
Synergetics, Inc.
------------------------------------------------------

On Tue, Sep 23, 2008 at 5:56 AM, rfwatson <rfw...@gm...> wrote:
> Hello,
>
> I am using matplotlib in combination with QT4 as part of an audio
> application I am building. Part of this involves plotting an
> oscilloscope-style display (time vs intensity) for sets of raw audio data,
> which I have through necessity converted to arrays of floating point data.
>
> The problem I have is that Pylab/QT slow down an unacceptable amount once
> the amount of audio is more than a few seconds long. This is not too
> surprising - typically a minute of stereo audio data will have 44100 * 60 *
> 2 = 5292000 points. I need to deal with, at minimum, 15 minute clips
> efficiently
Do you typically plot a large number of points, only a subset of which
are in your viewport? If so, the "clipped line" demo may be useful to
you:
http://matplotlib.sourceforge.net/examples/pylab_examples/clippedline.py
If you are trying to plot a large number of dense points all in the
same viewport, then you will need to decimate the data before
plotting.
JDH

On Tue, Sep 23, 2008 at 9:46 AM, Roland Hauff <rh...@ya...> wrote:
> I'm reading a serial port and plotting the acquired data using TKagg with the plot() command. This gives me a nice graphical screen that updates as the data arrives. What I would like to do is be able to pause the entire program occasionally as I need to make changes on the system that the RS232 is reading, then begin plotting again. Is there a way to get a pause button the TKAgg toolbar?
Yes, take a look at the embedding_in_tk*.py examples at
http://matplotlib.sourceforge.net/examples/user_interfaces/

On Tue, Sep 23, 2008 at 10:28 AM, Michael Hearne <mh...@us...> wrote:
> I installed the freetype-devel libraries and this problem went away.
>
Any chance you also installed tk-devel or tcl-devel? I can't see how
the addition of the freetype headers would fix a tk problem.
JDH

I installed the freetype-devel libraries and this problem went away.
--Mike
Michael Hearne wrote:
> All: I am trying to build matplotlib 0.98.3 on a Red Hat Enterprise 5 
> linux box. I have Tkinter support compiled into my 
> /usr/local/bin/python installation (at least "import Tkinter" raises 
> no exceptions). However, when I try to build matplotlib using 
> "/usr/local/bin/python setup.py build", I get the output below. Any 
> hints? Is this my fault, or a bug in setup.py?
>
> Thanks,
>
> Mike
>
> ============================================================================ 
>
> BUILDING MATPLOTLIB
> matplotlib: 0.98.3
> python: 2.5.2 (r252:60911, Sep 15 2008, 16:18:30) [GCC
> 4.1.2 20071124 (Red Hat 4.1.2-42)]
> platform: linux2
>
> REQUIRED DEPENDENCIES
> numpy: 1.1.0
> freetype2: found, but unknown version (no pkg-config)
> * WARNING: Could not find 'freetype2' headers 
> in any
> * of '/usr/local/include', '/usr/include', '.',
> * '/usr/local/include/freetype2',
> * '/usr/include/freetype2', './freetype2'.
>
> OPTIONAL BACKEND DEPENDENCIES
> libpng: 1.2.10
> Traceback (most recent call last):
> File "setup.py", line 125, in <module>
> if check_for_tk() or (options['build_tkagg'] is True):
> File "/home/mhearne/build/matplotlib-0.98.3/setupext.py", line 841, 
> in check_for_tk
> explanation = add_tk_flags(module)
> File "/home/mhearne/build/matplotlib-0.98.3/setupext.py", line 1101, 
> in add_tk_flags
> module.libraries.extend(['tk' + tk_ver, 'tcl' + tk_ver])
> UnboundLocalError: local variable 'tk_ver' referenced before assignment
>
-- 
------------------------------------------------------
Michael Hearne
mh...@us...
(303) 273-8620
USGS National Earthquake Information Center
1711 Illinois St. Golden CO 80401
Senior Software Engineer
Synergetics, Inc.
------------------------------------------------------

I'm reading a serial port and plotting the acquired data using TKagg with the plot() command. This gives me a nice graphical screen that updates as the data arrives. What I would like to do is be able to pause the entire program occasionally as I need to make changes on the system that the RS232 is reading, then begin plotting again. Is there a way to get a pause button the TKAgg toolbar?
Thanks!
 

I'm reading a serial port and plotting the acquired data using TKagg with the plot() command. This gives me a nice graphical screen that updates as the data arrives. What I would like to do is be able to pause the entire program occasionally as I need to make changes on the system that the RS232 is reading, then begin plotting again. Is there a way to get a pause button the TKAgg toolbar?
Thanks!
 

rfwatson wrote:
> Hello,
>
> I am using matplotlib in combination with QT4 as part of an audio 
> application I am building. Part of this involves plotting an 
> oscilloscope-style display (time vs intensity) for sets of raw audio 
> data, which I have through necessity converted to arrays of floating 
> point data.
>
> The problem I have is that Pylab/QT slow down an unacceptable amount 
> once the amount of audio is more than a few seconds long. This is not 
> too surprising - typically a minute of stereo audio data will have 
> 44100 * 60 * 2 = 5292000 points. I need to deal with, at minimum, 15 
> minute clips efficiently
>
> I have tried downsampling the audio dramatically and although this 
> helps a little, it is not enough for really large data sets. 
> Downsampling also reduces the accuracy of any editing of the audio, so 
> it's not the ideal solution.
Numpy slicing will let you create a subsampled (without interpolation) 
view on the data that you could send to matplotlib, and still maintain 
the original data for editing/listening purposes.
For example: audio[::64] will create a view that skips every 64 data 
points.
I don't know if skipping will produce adequate results for you vs. 
proper downsampling, however, but it's worth a try.
I remember SoundForge (at least a few years ago), used to downsample the 
data for display purposes and cache that to a file alongside the 
high-resolution audio. That suggests to me that any sort of 
downsampling on-the-fly may just be inherently too slow.
Remember, also, that matplotlib is drawing *actual* lines for its plots, 
which implies "stroking" (generating a polygon from moving an imaginary 
pen along the ideal line so that it can be filled). I suspect many 
audio editors take a much simpler approach, by drawing vertical 1-pixel 
wide strokes whose height is determined based on the average of the data 
within that pixel. That would be much more efficient for high-sample 
rate data than what matplotlib currently does. This is something to 
think about including in matplotlib for the future, but not something it 
currently does.
>
> I've read about 'data clipping' functionality in matplotlib, but can't 
> seem to get it working - has it been removed?
It should work with any of the Agg backends in 0.98.3 and additionally 
PDF, PS and SVG in SVN trunk. It should increase the speed, but on the 
other hand, large data is large data and the system still needs to 
iterate through all of it to determine which points to ignore.
Hope that helps in some way,
Mike
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Hi,
I'm not an expert, but I got the attached script to do what you need ( at 
least as I understand it). It isn't quite nice, because I need interactive 
mode turned on for proper value in the xtick labels in order to modify them. 
Maybe it is a kind of beginning for a good solution or maybe a proper 
solution is out there.
regards Matthias
On Thursday 11 September 2008 22:59:31 johnny_c wrote:
> Hi,
>
> I have a contour plot with a log scale on the x and y axes and I would
> like it to read "10^1 10^2 10^3 10^4". How would I go about doing this?
>
> Here's how I'm currently making the plot..
>
> contour( log10(x), log10(y), z )
>
> This only displays something like "0 1 2 3 4".
>
> Any suggestions?
>
> If there is a really obvious solution to this, then I apologize, but I
> can't seem to figure it out.
> Thanks

Hello,
I am using matplotlib in combination with QT4 as part of an audio
application I am building. Part of this involves plotting an
oscilloscope-style display (time vs intensity) for sets of raw audio data,
which I have through necessity converted to arrays of floating point data.
The problem I have is that Pylab/QT slow down an unacceptable amount once
the amount of audio is more than a few seconds long. This is not too
surprising - typically a minute of stereo audio data will have 44100 * 60 *
2 = 5292000 points. I need to deal with, at minimum, 15 minute clips
efficiently
I have tried downsampling the audio dramatically and although this helps a
little, it is not enough for really large data sets. Downsampling also
reduces the accuracy of any editing of the audio, so it's not the ideal
solution.
I've read about 'data clipping' functionality in matplotlib, but can't seem
to get it working - has it been removed?
If so, does anybody have any ideas as to the sort of approach I could take
to solve this?
Thanks
Rob

Jeff,
I still don't know how to either remove this artifact or fill my arrays with
values to remove empty regions, and I'll make a last attempt to resolve it
I uploaded a data file here: http://scqp.ulb.ac.be/20080821.b56
The actual code snippet is here:
http://snipplr.com/view/8307/map-plotting-python-code-temporary/
I hope you'll be able to reproduce it, I set the cmap to winter for you to
see the gap... setting it to hot will make the grayish border visible in
high resolution by zooming it... I think the border (not the empty zone)
could be an artifact with the hot colormap
Antoine De Pauw
Collaborateur de recherches, Informatique - Research collaborator, IT
Laboratoire de chimie quantique et photophysique - Quantum chemistry and
photophysics laboratory
Université Libre de Bruxelles - ULB
-----Original Message-----
From: Jeff Whitaker [mailto:js...@fa...] 
Sent: lundi 22 septembre 2008 13:59
To: De Pauw Antoine
Cc: 'John Hunter'; 'Matplotlib Users'
Subject: Re: [Matplotlib-users] Information request
De Pauw Antoine wrote:
> Jeff,
>
> I included here a figure where you'll see the border problem for imshow in
> my case
>
> http://img217.imageshack.us/img217/5240/testfigzp3.png
>
> The border wraps at -180 and 180 to form the white line
>
> PS: it is atmospheric ice and not SO2, I just omitted to change the title
^^
>
> Antoine De Pauw
> Collaborateur de recherches, Informatique - Research collaborator, IT
> Laboratoire de chimie quantique et photophysique - Quantum chemistry and
> photophysics laboratory
> Université Libre de Bruxelles - ULB
> 
Antoine: I hate to keep repeating myself - but we can't do much if you 
don't provide a self-contained script, that I can run, which reproduces 
the problem. My guess is that the line along the dateline, and the 
point at the South Pole are missing values (which griddata set to 
missing because they are outside the extent of the data) - but that's 
just a guess until I can reproduce it.
-Jeff
>
> -----Original Message-----
> From: Antoine De Pauw [mailto:and...@ul...] 
> Sent: jeudi 18 septembre 2008 17:23
> To: Jeff Whitaker; and...@ul...
> Cc: 'John Hunter'; 'Matplotlib Users'
> Subject: re:Re: [Matplotlib-users] Information request
>
> Jeff,
>
> No the example doesn't show that line
>
> If I reduce the amount of data, the border will be on every side of the
plot
>
> I'll show you an orthographic plot with no maskinf tomorrow and you will
see
> the problem easily, it wraps in a white line along the 0° meridian and a
> white circle in the pole
>
> I think it's the imshow layer that is not totally transparent on the map
> background.. I tried every trick I could for example to put some
zero-valued
> points on each corner to make imshow interpolate correctly the sides, but
> that doesn't make any difference
>
> 
>> De Pauw Antoine wrote:
>> 
>>> Jeff,
>>>
>>> Yes they disappear, and they fluctuate with the interpolation method
used
>>>
>>> For example, nearest interpolation don't show the line
>>>
>>> Also, if I reduce the grid resolution, the line is thicker, and if I use
>>> 
> a
> 
>>> masked array to get rid of undesired values, the border shows really
>>> strongly
>>>
>>> Here's an example everyone will see:
>>>
>>> http://img225.imageshack.us/img225/2671/testfigep2.png
>>>
>>> (everything except the clouds is noise)
>>>
>>> Antoine De Pauw
>>> Collaborateur de recherches, Informatique - Research collaborator, IT
>>> Laboratoire de chimie quantique et photophysique - Quantum chemistry and
>>> photophysics laboratory
>>> Université Libre de Bruxelles - ULB
>>> 
>>> 
>> Antoine: Sorry to seem dense, but I don't see anything wrong with that 
>> plot. I see a white border along the north and south pole, but I 
>> intrepret that to be missing values. However, my eyes are notoriously 
>> bad. I'd like to be to run a script that generates the artifacts 
>> myself, so I can zoom in and see the problem myself. Does the 
>> griddata_demo.py script show the same problem for you?
>>
>> -Jeff
>> 
>>> -----Original Message-----
>>> From: Jeff Whitaker [mailto:js...@fa...] 
>>> Sent: mercredi 17 septembre 2008 19:05
>>> To: John Hunter
>>> Cc: De Pauw Antoine; Matplotlib Users
>>> Subject: Re: [Matplotlib-users] Information request
>>>
>>> John Hunter wrote:
>>> 
>>> 
>>>> On Wed, Sep 17, 2008 at 11:54 AM, John Hunter <jd...@gm...>
wrote:
>>>>
>>>> 
>>>> 
>>>> 
>>>>> Attached is a screenshot (zoom.png) from the gimp, zoomed in near the
>>>>> axes border. The black horizontal line is the top axes border, the
>>>>> horizontal grey line is the artifact, the vertical dashed line is a
>>>>> grid line. I don't know if this offers a clue, but if you look at a
>>>>> zoom in the upper right corner, the grey line seems to break up and
>>>>> curve down and to the right (corner.png)
>>>>> 
>>>>> 
>>>>> 
>>>> Sorry, screwed up corner.png (I attached the original and not the
>>>> screenshot). The correct screenshot is attached
>>>> 
>>>>
>>>>
>>>> 
>>>> 
>>> John: OK, now I finally see it. Antoine: Do these artifacts 
>>> disappear if you comment out the imshow call?
>>>
>>> -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
>>
>>
>>
>> 
>
>
> 
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449
325 Broadway Boulder, CO, USA 80305-3328