matplotlib-devel Mailing List for matplotlib (Page 3)

Eric Firing wrote:
> Jeff,
>
> Basemap methods like plot() include a "draw_if_interactive" command, 
> followed by a call to the set_axes_limits() method, which ends with
>
>           # force draw if in interactive mode.
>          if is_interactive():
>              figManager = _pylab_helpers.Gcf.get_active()
>              figManager.canvas.draw()
>
> It seems to me that you could eliminate all those "draw_if_interactive" 
> blocks from plot etc., and replace the end block of set_axes_limits() with
>
>          if is_interactive():
>              import matplotlib.pyplot as plt
>              plt.draw_if_interactive()
>
> The advantages would be reduced clutter in the drawing methods, and 
> consistent use of draw_if_interactive.  I think the latter would make 
> interactive running of functions and subclasses built on basemap more 
> efficient by reducing redundant draw operations.
>
> It also looks like at least most of the operations in set_axes_limits 
> really need to be done only once (although I have not checked this 
> carefully).  Instead of repeating them with every call to a plotting 
> method, the basemap instance could keep a list of hashes of axes objects 
> on which the operations have already been run, and use that to prevent 
> duplication.
>
> Nothing urgent here--just some ideas that occur to me while working with 
> basemap.  If you think any are worth pursuing, and you want me to take a 
> shot at it, let me know.
>
> Eric
>
>
>   
Eric:  You are right, that could be done much more efficiently.  I'm 
stuck in the U.K. waiting for the volcanic dust to clear, so if you want 
to take a shot at it go ahead.

-Jeff

Jeff,

Basemap methods like plot() include a "draw_if_interactive" command, 
followed by a call to the set_axes_limits() method, which ends with

          # force draw if in interactive mode.
         if is_interactive():
             figManager = _pylab_helpers.Gcf.get_active()
             figManager.canvas.draw()

It seems to me that you could eliminate all those "draw_if_interactive" 
blocks from plot etc., and replace the end block of set_axes_limits() with

         if is_interactive():
             import matplotlib.pyplot as plt
             plt.draw_if_interactive()

The advantages would be reduced clutter in the drawing methods, and 
consistent use of draw_if_interactive.  I think the latter would make 
interactive running of functions and subclasses built on basemap more 
efficient by reducing redundant draw operations.

It also looks like at least most of the operations in set_axes_limits 
really need to be done only once (although I have not checked this 
carefully).  Instead of repeating them with every call to a plotting 
method, the basemap instance could keep a list of hashes of axes objects 
on which the operations have already been run, and use that to prevent 
duplication.

Nothing urgent here--just some ideas that occur to me while working with 
basemap.  If you think any are worth pursuing, and you want me to take a 
shot at it, let me know.

Eric

2010/4/16 David Kremer <dav...@gm...>:
> I would like to know how to find informations about how pyplot, imshow
> and contourf, contour functions are working.

Have a look at site-packages/matplotlib/axes.py in your Python distro,
search for "def imshow" or "def contourf".  You will be directed by
the code in your exploration, I guess.

Sorry, but as your question is quite general, the reply is so too :-/

Good luck,
Friedrich

P.S.: This functions are directly called by the thin wrappers
comprising the pyplot interface.

I went ahead an implemented the close events. These work for me on the
following backends that I was able to test: TkAgg, Wx/WxAgg, Qt4Agg,
Gtk/GtkAgg.

I can't test Cocoa or PyQt3, so I didn't implement. All that is needed
is to add a call (preferably on a FigureCanvasBase subclass) that
calls the FigureCanvasBase.close_event().

Ryan

On Thu, Apr 15, 2010 at 5:18 PM, Ryan May <rm...@gm...> wrote:
> Hi,
>
> Does anyone know if there's a matplotlib event that fires when a
> figure window is closed? I can't seem to find one.
>
> If there's not one, any I shouldn't add one? I need to stop my
> animation timers when the figure is closed.
>
> Ryan
>
> --
> Ryan May
> Graduate Research Assistant
> School of Meteorology
> University of Oklahoma
>



-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

Update:

I just tried "make -f make.osx fetch deps mpl_install", which gave me the following results:

python2.6 -c 'import urllib; urllib.urlretrieve("http://www.zlib.net/zlib-1.2.3.tar.gz", "zlib-1.2.3.tar.gz")'  &&\
	python2.6 -c 'import urllib; urllib.urlretrieve("http://downloads.sourceforge.net/project/libpng/libpng-stable/1.2.39/libpng-1.2.39.tar.gz", "libpng-1.2.39.tar.gz")' &&\
	python2.6 -c 'import urllib; urllib.urlretrieve("http://download.savannah.gnu.org/releases/freetype/freetype-2.3.11.tar.bz2", "freetype-2.3.11.tar.bz2")'
export PKG_CONFIG_PATH="/Users/mhearne/build make -f make.osx fetch deps mpl_install/lib/pkgconfig" &&\
	rm -rf zlib-1.2.3 &&\
	tar xvfj zlib-1.2.3.tar.gz &&\
	cd zlib-1.2.3 &&\
	export MACOSX_DEPLOYMENT_TARGET=10.6 &&\
	export CFLAGS="-arch i386 -arch x86_64 -I/Users/mhearne/build make -f make.osx fetch deps mpl_install/include -I/Users/mhearne/build make -f make.osx fetch deps mpl_install/include/freetype2 -isysroot /Developer/SDKs/MacOSX10.6.sdk" &&\
	export LDFLAGS="-arch i386 -arch x86_64 -L/Users/mhearne/build make -f make.osx fetch deps mpl_install/lib -syslibroot,/Developer/SDKs/MacOSX10.6.sdk" &&\
	./configure --prefix=/Users/mhearne/build make -f make.osx fetch deps mpl_install&&\
	MACOSX_DEPLOYMENT_TARGET=10.6 CFLAGS="-arch i386 -arch x86_64 -I/Users/mhearne/build make -f make.osx fetch deps mpl_install/include -I/Users/mhearne/build make -f make.osx fetch deps mpl_install/include/freetype2 -isysroot /Developer/SDKs/MacOSX10.6.sdk" LDFLAGS="-arch i386 -arch x86_64 -L/Users/mhearne/build make -f make.osx fetch deps mpl_install/lib -syslibroot,/Developer/SDKs/MacOSX10.6.sdk" make -j3 install&& \
	unset MACOSX_DEPLOYMENT_TARGET
bzip2: (stdin) is not a bzip2 file.
tar: Child returned status 2
tar: Error exit delayed from previous errors
make: *** [zlib] Error 2

Begin forwarded message:

> From: Michael Hearne <mh...@us...>
> Date: April 16, 2010 12:25:50 PM MDT
> To: mat...@li...
> Subject: [matplotlib-devel] Building from svn on OS X, and nabble
> 
> First the easy one:
> 
> When I click on the link for the archives on the matplotlib page:
> http://www.nabble.com/matplotlib---users-f2906.html
> 
> I get sent to this page:
> http://www.nabble.com/-td2885.html#a2906
> 
> which is in some Slavic looking language, so I can't tell what it's a forum for, but it's probably not matplotlib.
> 
> Anyway.
> 
> My _real_ question is about building from svn on OS X.
> 
> (Before anyone asks me _why_ I'm building on OS X, it's because there is a PDF bug in the current released version which I need to avoid).
> 
> There are instructions to modify make.osx to include a local directory where dependencies are downloaded, which I did.  There aren't any further instructions, however, so I've building/installing using setup.py,  which runs, but has a run-time error regarding free-type fonts that I have encountered before.  I've also tried running make with various arguments, none of which appear to do anything useful.
> 
> What are the proper build/install commands for OS X once the make.osx file has been edited?
> 
> Thanks,
> 
> Mike
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

First the easy one:

When I click on the link for the archives on the matplotlib page:
http://www.nabble.com/matplotlib---users-f2906.html

I get sent to this page:
http://www.nabble.com/-td2885.html#a2906

which is in some Slavic looking language, so I can't tell what it's a forum for, but it's probably not matplotlib.

Anyway.

My _real_ question is about building from svn on OS X.

(Before anyone asks me _why_ I'm building on OS X, it's because there is a PDF bug in the current released version which I need to avoid).

There are instructions to modify make.osx to include a local directory where dependencies are downloaded, which I did.  There aren't any further instructions, however, so I've building/installing using setup.py,  which runs, but has a run-time error regarding free-type fonts that I have encountered before.  I've also tried running make with various arguments, none of which appear to do anything useful.

What are the proper build/install commands for OS X once the make.osx file has been edited?

Thanks,

Mike

Hello.

I would like to know how to find informations about how pyplot, imshow
and contourf, contour functions are working.

I'm looking for a way to derive/improve this functions because I dont
know how to make my plot properly otherly.

Thank you very much.

Greetings,

David Kremer

First of all, thanks, klukas for the useful piece of code.

Jae-Joon Lee wrote:
> On Mon, Mar 29, 2010 at 12:30 PM, Jeff Klukas <kl...@wi...> wrote:
>> # Create BrokenAxes with bottom from 0 to 5 and top from 30 to 35
>> ax = plt.broken_axes(ybounds=[0.,5.,30.,35.])
>> # Plot a line onto BOTH subaxes
>> ax.plot(range(35),range(35))
>>
>> The call to plot would get routed through __getattribute__, which
>> would then call plot for each of the subaxes.  This would be much more
>> intuitive than my existing breaky solution, where you have to loop
>> over all subaxes and plot on each individually.
>>
> 
> How do you want to handle
> 
> l1, = ax.plot(range(35), range(35))
> l1.set_color("r")
> 
> then?
> 

Well, I guess BrokenAxes.plot should return a list of lines instead of a
line in ll.
i.e. something like "[[x.lines[-1] for x in ax.subaxes]]"
would replace "[ax.lines[-1]]" as the return value.
Better yet, instead of a list we should have a "vector-type" proxy
container that should transfer method calls to the contained items.

> I think keeping two (or more) separate artists for each axes while an
> user think there is only one artist (because only one axes is exposed
> to the user) is not a good idea.

Ideally this should really be one artist.
However from JDH's response I understand this would be harder to
implement (using custom transforms or something). Maybe emulating one
using the current implementation (as I suggested above) is good enough.

Meanwhile, this redundant looping for each plot call is annoying, so I
can offer the following compromise: store the subaxes in the parent
(broken)Axes (add "self._subaxes = subaxes" before returning from breakx
and breaky), then add a new plot_subs method:

def plot_subs(self,*args,**keys):
    for sub in self._subaxes:
        res = sub.plot(*args,**keys)
    return res

This is a simplified version, returning just the lines of the last
subaxes, but at least this way you can avoid the looping.


 Regards,
     Amit A.

Hi,

Does anyone know if there's a matplotlib event that fires when a
figure window is closed? I can't seem to find one.

If there's not one, any I shouldn't add one? I need to stop my
animation timers when the figure is closed.

Ryan

-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

You should probably avoid sending the same message to the list twice.  You run the risk of only annoying the developers and not getting any real help.

The mplot3d axes code is in a major need of refactoring.  There are very few developers who have worked on the mplot3d code.  But at the same time, you will find that the code is much smaller, and more accessible than you might imagine.  I found it very easy to fix some bugs in the bar3d function that I needed for my project.

So I suggest you look into fixing the bug yourself.  It is pretty easy to submit patches to the development team.
-Ben


From: Martin Bothe [mailto:mar...@ba...]
Sent: Thursday, April 15, 2010 11:11 AM
To: mat...@li...
Subject: [matplotlib-devel] Bug in mplot3d set_xlim3d, set_ylim3d, set_zlim3d

Hello matplotlib-devs,

I found what I think is a bug. If you run the following code, you'll see a simple figure with a graph at the position where the x-axis should be.
Unfortunately this is not the case, even if set_xlim3d(0,10) is set, so it should be at the edge of the plot.

The code:

import matplotlib as mpl
from mpl_toolkits.mplot3d import Axes3D
import matplotlib.pyplot as plt

fig = plt.figure()
ax = Axes3D(fig)
x = range(11)
y = [0]*11
z = [0]*11
ax.plot(x, y, z, label='X-axis position')
ax.set_xlim3d(0,10)
ax.set_ylim3d(0,10)
ax.set_zlim3d(0,10)
ax.legend()

I attached the figure it produces.

You can also see, that from the edge to the 2 of one of the axis is a longer distance than from 2 to 4 on the same axis.
A way to fix it is highly appreaciated.

Greetings from Berlin
Martin

Eric Firing wrote:
> I went ahead and committed your refactoring.  It seems to work fine.
> Contour.py was not pretty before the refactoring, and it is still not
> pretty, but I don't think it is much worse, if at all.  I have a vague sense
> that ideally it would be factored somewhat differently, but I don't seem to
> have the time or vision to pursue it right now, and maybe if I did, I would
> still run into a dead end.  So, let's proceed with what you have.  If
> inspiration strikes later, I suspect it won't be too hard to modify both
> contour and tricontour accordingly.

Understood.

I've attached the patch for the new triangular grid functionality.
I've altered it to use multiply-connected paths for filled contours
which has made the code a bit simpler overall.

Ian

Ian Thomas wrote:
> Eric Firing wrote:
>> I've only glanced so far, but one thing that caught my eye is your
>> documentation changes and code regarding the need for simply-connected
>> paths.  This is obsolete--mpl now handles multiply-connected paths.
> 
> Thanks for clarifying this, I now understand the 'point kinds' in
> cntr.c which I originally thought were for debug purposes.  It will
> make my code simpler in the end.
> 
>> A second initial suggestion is that you divide the work into two patches,
>> one of which provides the refactoring of existing code (presumably only in
>> contour.py), and a second which adds the new functionality.
> 
> Good idea.  I've attached the first patch which changes axes.py and
> contour.py, plus adds the new example contour_manual.py.  My approach
> to the refactoring is probably more of a C++ than pythonic way of
> thinking with derived classes that override base class methods, but it
> avoids changing much of the low level code and avoids code duplication
> when tricontour is added in.
> 
> Ian
> 

Ian,

I went ahead and committed your refactoring.  It seems to work fine. 
Contour.py was not pretty before the refactoring, and it is still not 
pretty, but I don't think it is much worse, if at all.  I have a vague 
sense that ideally it would be factored somewhat differently, but I 
don't seem to have the time or vision to pursue it right now, and maybe 
if I did, I would still run into a dead end.  So, let's proceed with 
what you have.  If inspiration strikes later, I suspect it won't be too 
hard to modify both contour and tricontour accordingly.

Eric

Eric, I've seen the comment "Why is the copy needed?" that you've added
to the axes' hist method. I think this was introduced by me some time
ago. Indeed, I think it is not really needed. If I remember correctly, I
had done the copying to avoid that the input x gets modified (I had bad
experience with that before), but I think we can avoid it?

Manuel

Hi,

I am pleased to announce the second release candidate of both Scipy 0.7.2
and NumPy 1.4.1. Please test, and report any problems on the NumPy or SciPy
list. I also want to specifically ask you to report success/failure with
other libraries (Matplotlib, Pygame, <your favorite lib here>) based on
NumPy or SciPy.

Binaries, sources and release notes can be found at
https://sourceforge.net/projects/numpy/files/
https://sourceforge.net/projects/scipy/files/


NumPy 1.4.1
==========
The main change over 1.4.0 is that datetime support has been removed. This
fixes the binary incompatibility issues between NumPy and other libraries
like SciPy and Matplotlib.

There are also a number of other bug fixes, and no new features.

Binaries for Python 2.5 and 2.6 are available for both Windows and OS X.


SciPy 0.7.2
=========
The only change compared to 0.7.1 is that the C sources for Cython code have
been regenerated with Cython 0.12.1. This ensures that SciPy 0.7.2 will work
with NumPy 1.4.1, while also retaining backwards compatibility with NumPy
1.3.0.

Note that the 0.7.x branch was created in January 2009, so a lot of fixes
and new functionality in current trunk is not present in this release.

Binaries for Python 2.6 are available for both Windows and OS X. Due to the
age of the code no binaries for Python 2.5 are available.


On behalf of the NumPy and SciPy developers,
Ralf

On Wed, Apr 14, 2010 at 2:18 AM, Gökhan Sever <gok...@gm...> wrote:
>
>
> On Tue, Apr 13, 2010 at 10:40 PM, Peter Butterworth <bu...@gm...>
> wrote:
>>
>> Hi,
>>
>> I have been unable to reproduce the problem on my system.
>>  matplotlib.__version__ : '0.99.3rc1' + Python 2.6.5 on Win32
>>
>> attached is a test example, could you please post the full error trace?
>> Is the text tab populated correctly with labels, does the problem
>> occur immediately or on clicking Apply ?
>
> Demo looks great and works without any issues. I think these updates and
> example should definitely committed into the svn. New users might find these
> additions so useful. I also see that it works well with multiple instances
> of same types.
>
> I[2]: plt.text(0.1,0.1, "mest")
>
> I[3]: plt.text(0.4,0.4, "test")
>
> I[4]: plt.text(0.9,0.9, "rest")
>
> For some unknown reason the error messages I got before disappeared when I
> tried your demo.
>
> Darren might be helpful at this point to submit the changes.

My time is completely spoken for this week. But I'll have a look this
weekend if some helpful person doesn't beat me to it.

Darren

On Tue, Apr 13, 2010 at 10:40 PM, Peter Butterworth <bu...@gm...>wrote:

> Hi,
>
> I have been unable to reproduce the problem on my system.
>  matplotlib.__version__ : '0.99.3rc1' + Python 2.6.5 on Win32
>
> attached is a test example, could you please post the full error trace?
> Is the text tab populated correctly with labels, does the problem
> occur immediately or on clicking Apply ?
>

Demo looks great and works without any issues. I think these updates and
example should definitely committed into the svn. New users might find these
additions so useful. I also see that it works well with multiple instances
of same types.

I[2]: plt.text(0.1,0.1, "mest")

I[3]: plt.text(0.4,0.4, "test")

I[4]: plt.text(0.9,0.9, "rest")

For some unknown reason the error messages I got before disappeared when I
tried your demo.

Darren might be helpful at this point to submit the changes.


>
> > Could the similar text-editing functionality be added for label and title
> > text? It would be nice to update them via these menus.
>
> yes, I believe it should be possible to add title and xlabel text
> objects to the texts tab.
>

Yes, this would be another nice addition.

Thanks for your efforts.


>
>
> On Tue, Apr 13, 2010 at 6:55 AM, Gökhan Sever <gok...@gm...>
> wrote:
> >
> >
> > On Sun, Apr 11, 2010 at 1:53 PM, Peter Butterworth <bu...@gm...>
> > wrote:
> >>
> >> I've now uploaded the final version for review at the sourceforge
> tracker
> >> :
> >>
> >>
> https://sourceforge.net/tracker/?func=detail&aid=2981606&group_id=80706&atid=560722
> >>
> >> figureoptions.py: modify plot options interactively (see attached
> >> screenshot)
> >> Requires PyQt4 installed
> >>
> >> Support of :
> >> - Axes (xy scale)
> >> - Legend
> >> - Lines
> >> - Patches (Rectangle, Ellipse, Polygon, dolphins...)
> >> - Texts
> >>
> >> Ignores :
> >> - Collections
> >>
> >> Limitations:
> >> - not available for multiple axes in the same subplot
> >
> > Hello,
> >
> > I couldn't make options in Texts tab working. I simply add a text by:
> >
> > plt.text(0,1, "test")
> >
> > Texts tab appears however nothing functions. I get errors ending with
> > "TypeError: 'str' object is not callable" in my each try.
> >
> >
> > --
> > Gökhan
>
> --
> thanks,
> peter butterworth
>



-- 
Gökhan

Hi,

I have been unable to reproduce the problem on my system.
 matplotlib.__version__ : '0.99.3rc1' + Python 2.6.5 on Win32

attached is a test example, could you please post the full error trace?
Is the text tab populated correctly with labels, does the problem
occur immediately or on clicking Apply ?

> Could the similar text-editing functionality be added for label and title
> text? It would be nice to update them via these menus.

yes, I believe it should be possible to add title and xlabel text
objects to the texts tab.


On Tue, Apr 13, 2010 at 6:55 AM, Gökhan Sever <gok...@gm...> wrote:
>
>
> On Sun, Apr 11, 2010 at 1:53 PM, Peter Butterworth <bu...@gm...>
> wrote:
>>
>> I've now uploaded the final version for review at the sourceforge tracker
>> :
>>
>> https://sourceforge.net/tracker/?func=detail&aid=2981606&group_id=80706&atid=560722
>>
>> figureoptions.py: modify plot options interactively (see attached
>> screenshot)
>> Requires PyQt4 installed
>>
>> Support of :
>> - Axes (xy scale)
>> - Legend
>> - Lines
>> - Patches (Rectangle, Ellipse, Polygon, dolphins...)
>> - Texts
>>
>> Ignores :
>> - Collections
>>
>> Limitations:
>> - not available for multiple axes in the same subplot
>
> Hello,
>
> I couldn't make options in Texts tab working. I simply add a text by:
>
> plt.text(0,1, "test")
>
> Texts tab appears however nothing functions. I get errors ending with
> "TypeError: 'str' object is not callable" in my each try.
>
>
> --
> Gökhan

-- 
thanks,
peter butterworth

On Sun, Apr 11, 2010 at 1:53 PM, Peter Butterworth <bu...@gm...>wrote:

> I've now uploaded the final version for review at the sourceforge tracker :
>
> https://sourceforge.net/tracker/?func=detail&aid=2981606&group_id=80706&atid=560722
>
> figureoptions.py: modify plot options interactively (see attached
> screenshot)
> Requires PyQt4 installed
>
> Support of :
> - Axes (xy scale)
> - Legend
> - Lines
> - Patches (Rectangle, Ellipse, Polygon, dolphins...)
> - Texts
>
> Ignores :
> - Collections
>
> Limitations:
> - not available for multiple axes in the same subplot
>

Hello,

I couldn't make options in Texts tab working. I simply add a text by:

plt.text(0,1, "test")

Texts tab appears however nothing functions. I get errors ending with
"TypeError: 'str' object is not callable" in my each try.

Could the similar text-editing functionality be added for label and title
text? It would be nice to update them via these menus.

-- 
Gökhan

On Mon, Sep 28, 2009 at 9:37 AM, William Stein <ws...@gm...> wrote:
>
> On Mon, Sep 28, 2009 at 9:35 AM, John Hunter <jd...@gm...> wrote:
>> On Mon, Sep 28, 2009 at 11:14 AM, John Hunter <jd...@gm...> wrote:
>>
>>> But even simple tests are failing with::
>>>
>>> jdh2358@bsd:~> LD_LIBRARY_PATH=~/devtest/lib/
>>> PYTHONPATH=~/devtest/lib/python2.6/site-packages/ /usr/bin/python -c
>>> 'import matplotlib; matplotlib.use("Agg"); from matplotlib.pyplot
>>> import *; plot([1,2,3]); savefig("test")'
>>> Traceback (most recent call last):
>>>  File "<string>", line 1, in <module>
>>>  File "/Users/jdh2358/devtest//lib/python2.6/site-packages/matplotlib/pyplot.py",
>>> line 7, in <module>
>>>    from matplotlib.figure import Figure, figaspect
>>>  File "/Users/jdh2358/devtest//lib/python2.6/site-packages/matplotlib/figure.py",
>>> line 16, in <module>
>>>    import artist
>>>  File "/Users/jdh2358/devtest//lib/python2.6/site-packages/matplotlib/artist.py",
>>> line 6, in <module>
>>>    from transforms import Bbox, IdentityTransform, TransformedBbox,
>>> TransformedPath
>>>  File "/Users/jdh2358/devtest//lib/python2.6/site-packages/matplotlib/transforms.py",
>>> line 34, in <module>
>>>    from matplotlib._path import affine_transform
>>> ImportError: /Users/jdh2358/devtest/lib/python2.6/site-packages/matplotlib/_path.so:
>>> no appropriate 64-bit architecture (see "man python" for running in
>>> 32-bit mode)
>>>
>>> I'm attaching my build output in case anyone sees anything that might
>>> be triggering this 32bit/64bit problem (see attached for full output).
>>>  I did not rebuild numpy and this may be the problem since the failure
>>> is in the _path module.  I'll give that a try next
>>
>>
>> Same issue with numpy HEAD
>
> One thing to keep in mind is that the default for GCC on OS X 10.6 is
> to build 64-bit binaries.   With OS X 10.5 the default for GCC was to
> make 32-bit binaries.  (To get 64-bit you used to have to do "-m64",
> but that is now the default.)   So you really have to start from
> scratch.

I am now getting the exact same problem with pylab and FEMhub and Mac.
I used http://sagemath.org/packages/standard/matplotlib-0.99.1.p4.spkg:

ondrej@bsd:~/repos/femhub-0.9.9.beta3-mac(master)$ ./femhub
----------------------------------------------------------------------
| FEMhub Version 0.9.9.beta2, Release Date: 2010-04-02               |
| Type lab() for the GUI.                                            |
----------------------------------------------------------------------
In [1]: import pylab
/Users/ondrej/repos/femhub-0.9.9.beta3-mac/local/lib/python2.6/site-packages/matplotlib/rcsetup.py:117:
UserWarning: rcParams key "numerix" is obsolete and has no effect;
 please delete it from your matplotlibrc file
  warnings.warn('rcParams key "numerix" is obsolete and has no effect;\n'
/Users/ondrej/repos/femhub-0.9.9.beta3-mac/local/bin/sage-sage: line
203: 28516 Abort trap              sage-ipython "$@" -i



It's using the "bsd" Mac machine from William, I guess the same as
John was using above.


Has anybody figured out a solution? Apparently Sage must work on the
Mac, so it must be something different than just matplotlib? Some
other package, that we have in femhub, but not in Sage, or some
different version of something. Here is a list of packages that I have
installed:

ondrej@bsd:~/repos/femhub-0.9.9.beta3-mac(master)$ ./femhub -i
Currently installed packages:
blas-20070724
bzip2-1.0.5
cmake-2.6.2.p1
configobj-4.5.3
cython-0.12.1
dir-0.1
docutils-0.5.p0
femhub-lab-97141eb
fipy-2.1-eb4aacf
fortran-20071120.p8
freetype-2.3.5.p2
gnutls-2.2.1.p3
hermes2d-9bbfd39
ipython-bzr1174
jinja-1.2.p0
judy-1.0.5.p1
lapack-20071123.p1
libfemhub-78c07cb
libgcrypt-1.4.3.p2
libgpg_error-1.6.p2
libpng-1.2.35.p0
matplotlib-0.99.1.p4
mayavi-3.3.1.p2
mesa-7.4.4.p3
numpy-1.3.0.p2
pexpect-2.0.p3
prereq-0.3
pygments-0.11.1.p0
pyparsing-1.5.2
pysparse-1.1-6301cea
python-2.6.4.p7
python_gnutls-1.1.4.p7
readline-6.0
sage_scripts-3.4.2
scipy-0.7.p4
setuptools-0.6c9.p0
sfepy-2009.3
sphinx-0.6.3.p4
swig-1.3.36
sympy-5d78c29
termcap-1.3.1.p1
twisted-9.0.p2
vtk-cvs-20090316-minimal.p6
zlib-1.2.3.p5


Let me know if you have any hints what to try.

Ondrej

Eric Firing wrote:
> I've only glanced so far, but one thing that caught my eye is your
> documentation changes and code regarding the need for simply-connected
> paths.  This is obsolete--mpl now handles multiply-connected paths.

Thanks for clarifying this, I now understand the 'point kinds' in
cntr.c which I originally thought were for debug purposes.  It will
make my code simpler in the end.

> A second initial suggestion is that you divide the work into two patches,
> one of which provides the refactoring of existing code (presumably only in
> contour.py), and a second which adds the new functionality.

Good idea.  I've attached the first patch which changes axes.py and
contour.py, plus adds the new example contour_manual.py.  My approach
to the refactoring is probably more of a C++ than pythonic way of
thinking with derived classes that override base class methods, but it
avoids changing much of the low level code and avoids code duplication
when tricontour is added in.

Ian

Ian Thomas wrote:
> Hello all,
> 
> Attached is a patch file against svn head to add triangular grid
> plotting and contouring.  It will need some serious checking/reviewing
> before it can be added to MPL.  I've tested it on 32 and 64-bit Linux,
> but I don't use other operating systems very often.
> 
> Most of the new code is in a new directory lib/matplotlib/tri.  There
> is a Triangulation class to store an unstructured triangular grid for
> reuse; the user can either specify the triangles or allow
> matplotlib.delaunay to create a Delaunay triangulation.  There are
> three plotting functions: triplot to plot grid lines and points,
> tripcolor to draw a pseudoplot, and tricontour/tricontourf to
> calculate and draw contour lines and filled contours.  You can either
> pass in a Triangulation object to these functions, or pass in the x,y
> points, etc and have MPL create a temporary Triangulation for you (for
> convenience).
> 
> The underlying contouring code is C++, and I've used CXX to access it.
> 
> There are some changes to axes.py and pyplot.py to expose the new
> functionality, and changes to the build scripts to build the new C++
> module.  I've also changed contour.py, splitting the previous
> ContourSet class into ContourSet and a derived QuadContourSet so there
> is separate responsibility for creating contours (QuadContourSet) and
> storage/display (ContourSet).  ContourSet allows you to specify your
> own polygons to draw, which should allow easier extension to other
> contouring algorithms.  QuadContourSet is now used by contour/contourf
> to create contour lines/polygons for a quad grid and the base class
> stores and draws them.  The benefit of this approach is that
> QuadContourSet is a relatively small class, allowing the equivalent
> triangular grid contouring class TriContourSet to be similarly small,
> and there is little code duplication.
> 
> I've added examples to demonstrate the new functionality, including
> manually creating your own contours, and also a comparison between
> griddata and tricontourf to contour unstructured grids.
> 
> Both the C++ and python are documented, but as I'm not familiar with
> the relationship between pydoc strings and sphinx, you may need to
> guide me further to increase/reduce links between and duplication of
> pydocs.
> 
> All questions and comments gratefully received.
> Ian

Ian,

I've only glanced so far, but one thing that caught my eye is your 
documentation changes and code regarding the need for simply-connected 
paths.  This is obsolete--mpl now handles multiply-connected paths.  If 
you look in cntr.c, you will find a "reorder()" function which converts 
the simply-connected paths to multiply-connected paths, which render 
better, because they don't have the cuts.  (Maybe the core routines in 
cntr.c could be modified so that the multiply-connected paths would be 
generated directly, so that reorder() would not be needed; but I find 
those routines very difficult to follow, so writing reorder() was easier.)

A second initial suggestion is that you divide the work into two 
patches, one of which provides the refactoring of existing code 
(presumably only in contour.py), and a second which adds the new 
functionality.  This would make reviewing and debugging easier.  (Your 
contour_manual.py could also go in the first patch.)

Thanks for all the good work!

Eric

I've now uploaded the final version for review at the sourceforge tracker :
https://sourceforge.net/tracker/?func=detail&aid=2981606&group_id=80706&atid=560722

figureoptions.py: modify plot options interactively (see attached screenshot)
Requires PyQt4 installed

Support of :
- Axes (xy scale)
- Legend
- Lines
- Patches (Rectangle, Ellipse, Polygon, dolphins...)
- Texts

Ignores :
- Collections

Limitations:
- not available for multiple axes in the same subplot


> On Sat, Apr 3, 2010 at 6:23 AM, Gökhan Sever <gok...@gm...> wrote:
>> Hi Peter,
>>
>> Your previous addition looks fine here. Keep pinging probably someone should
>> commit your additions.

On Fri, Apr 9, 2010 at 12:16 AM, Peter Butterworth <bu...@gm...> wrote:
> Hi,
>
> I'm having trouble getting some properties that are easily set :
>
>
> leg=legend(loc=0)
> is there a way to retrieve the legend location ?

leg._loc

I'm not sure why it's given a leading '_' to signal a private
variable, since it's implemented as a property. I'd probably still use
it.

> In a similar vein :
> axis('scaled')
> is there a way to retrieve the "scaled" property ?

Not really, since scaled isn't stored, but is merely a helper for

self.set_aspect('equal', adjustable='box', anchor='C')
self.set_autoscale_on(False)

You can get all of these properties individually:
ax = plt.gca()
ax.get_aspect()
ax.get_adjustable()
ax.get_anchor()
ax.get_autoscale_on()

Ryan

-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

Hello all,

Attached is a patch file against svn head to add triangular grid
plotting and contouring.  It will need some serious checking/reviewing
before it can be added to MPL.  I've tested it on 32 and 64-bit Linux,
but I don't use other operating systems very often.

Most of the new code is in a new directory lib/matplotlib/tri.  There
is a Triangulation class to store an unstructured triangular grid for
reuse; the user can either specify the triangles or allow
matplotlib.delaunay to create a Delaunay triangulation.  There are
three plotting functions: triplot to plot grid lines and points,
tripcolor to draw a pseudoplot, and tricontour/tricontourf to
calculate and draw contour lines and filled contours.  You can either
pass in a Triangulation object to these functions, or pass in the x,y
points, etc and have MPL create a temporary Triangulation for you (for
convenience).

The underlying contouring code is C++, and I've used CXX to access it.

There are some changes to axes.py and pyplot.py to expose the new
functionality, and changes to the build scripts to build the new C++
module.  I've also changed contour.py, splitting the previous
ContourSet class into ContourSet and a derived QuadContourSet so there
is separate responsibility for creating contours (QuadContourSet) and
storage/display (ContourSet).  ContourSet allows you to specify your
own polygons to draw, which should allow easier extension to other
contouring algorithms.  QuadContourSet is now used by contour/contourf
to create contour lines/polygons for a quad grid and the base class
stores and draws them.  The benefit of this approach is that
QuadContourSet is a relatively small class, allowing the equivalent
triangular grid contouring class TriContourSet to be similarly small,
and there is little code duplication.

I've added examples to demonstrate the new functionality, including
manually creating your own contours, and also a comparison between
griddata and tricontourf to contour unstructured grids.

Both the C++ and python are documented, but as I'm not familiar with
the relationship between pydoc strings and sphinx, you may need to
guide me further to increase/reduce links between and duplication of
pydocs.

All questions and comments gratefully received.
Ian

Hi,

I'm having trouble getting some properties that are easily set :


leg=legend(loc=0)
is there a way to retrieve the legend location ?

In a similar vein :
axis('scaled')
is there a way to retrieve the "scaled" property ?

If no methods/properties are available in the default API is it
possible to implement them easily ?