[SciPy-Dev] schedule for scipy 0.9.0 [scipy.interpolate]
Charles R Harris
Fri Nov 12 10:42:57 CST 2010
On Fri, Nov 12, 2010 at 9:21 AM, Pauli Virtanen <firstname.lastname@example.org> wrote:
> Fri, 12 Nov 2010 23:45:39 +0800, Ralf Gommers wrote:
> > I'm interested to hear what you think about releasing scipy 0.9.0 in the
> > near future, and if you have any things that should go in or be fixed
> > for 0.9.0. If we want to keep to a ~6 month release schedule then we
> > should branch around the end of this month and have a final release in
> > January.
> Sounds OK to me. I think we should try to time it so that it gets in
> Some tasks that would be nice to do before that in scipy.interpolate:
> - Write a interpolation routine for N-d *structured* interpolation.
> (ndimage.map_coordinates is difficult to find, so it would be useful
> to have an interpolation-oriented routine for that in
> - Deprecate interp2d, as it does not work well for most problems,
> and its calling convention is a bit wonky. People should use either
> `griddata` or splines depending on what they want to do.
> - Clean up the spline routines:
> - We have two incompatible implementations for 1-D splines there,
> on from FITPACK, and a pure-Python one by Travis. I don't remember
> if one of them has an advantage over the other.
Which is the pure python one? The interpolate.py module is, I believe,
Pearu's and uses fitpack. However, there are two interfaces to fipack, one
generated by f2py, and another handwritten in C. We probably want to keep
the f2py interface but the handwritten interface is a bit higher level.
Fitpack uses b-splines, which isn't the fastest representation to evaluate
but is essential for least squares.
I agree that it would be nice to rationalize the spline packages, I'm not
sure we can do that for 9.0.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-Dev