For a comprehensive list of changes, see Releases.
v0.16.1
Fixes:
- Fix hessianwith ForwardDiff.jl for scaled interpolants (#628)
v0.16
Breaking changes:
- getindexfor AbstractInterpolations only accepts integers (#579), deprecated since (#226)
- gradientand- hessianare once again no longer exported (#623)
- Fix free boundary condition on Cubic(#616)
- Compatible with Julia versions 1.9 and later
v0.15
Breaking changes:
- Compatible with Julia versions 1.6 and later
v0.14.0
Breaking changes:
Implement inplace GriddedInterpolation (#496, for #495)
- interpolatenow copies the coefficients for- GriddedInterpolation.
- interpolate!now does not copy the coefficients for- GriddedInterpolation.
- The third argument of GriddedInterpolationdescribes the array type of the coefficients rather than the element type ofArray.
v0.9.0
Breaking changes:
- gradientand- hessianare no longer exported; use- Interpolations.gradientand- Interpolations.hessian.
- interpolateobjects now check bounds, and throw an error if you try to evaluate them at locations beyond the edge of their interpolation domain; use- extrapolateif you need out-of-bounds evaluation
- For quadratic and cubic interpolation, interpolate!now returns an object whose axes are narrowed by the amount of padding needed on the array edges. This preserves correspondence between input indices and output indices. See https://julialang.org/blog/2017/04/offset-arrays for more information.
- The parametrization of some types has changed; this does not affect users of the "exported" interface, but does break packages that performed manual construction of explicit types.
Changes with deprecation warnings:
- itp[i...]should be replaced with- itp(i...).
- OnGridand- OnCellshould now be placed inside the boundary condition (e.g.,- Flat(OnGrid())), and should only be used for quadratic and cubic interpolation.
- the extrapolation boundary condition Linearwas changed toLine, to be consistent with interpolation boundary conditions.
Advance notice of future changes:
- In future versions itp[i...]may be interpreted with reference to the parent array's indices rather than the knots supplied by the user (relevant forscaleandGridded). If you fix the existing deprecation warnings then you should be prepared for this change.