Re: [matplotlib-devel] Contouring unstructured triangular grids

2010-04-15 Thread Eric Firing
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

--
Download Intel® 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
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


[matplotlib-devel] Release candidate 2 for NumPy 1.4.1 and SciPy 0.7.2

2010-04-15 Thread Ralf Gommers
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, ) 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
--
Download Intel® 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
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] Bug in mplot3d set_xlim3d, set_ylim3d, set_zlim3d

2010-04-15 Thread Ben Axelrod
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:martin.bo...@bam.de]
Sent: Thursday, April 15, 2010 11:11 AM
To: matplotlib-devel@lists.sourceforge.net
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
--
Download Intel® 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
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


[matplotlib-devel] Close events

2010-04-15 Thread Ryan May
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

--
Download Intel® 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
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel