.NET Opensource

Hi 

I've downloaded the latest from svn and I'm playing around with the new interpolation functionality. I'm finding it pretty easy to use and was just wondering what the planned features are. One feature which is of interest to me is the "not-a-knot" boundary condition for splines.

Keep up the great work! 

The Interpolation.CreateNaturalCubicSpline method takes a IList<double> as argument. Vector does not have an implicit cast to IList.

Therefore I need to write:

Interpolation.CreateNaturalCubicSpline(((double[)x).ToList(), ((double[)y).ToList());

instead of:

Interpolation.CreateNaturalCubicSpline(x, y); 

I quickly tried to add an implicit cast to Vector, but VS gave me the following error:

Error    1    'MathNet.Numerics.LinearAlgebra.Vector.implicit operator System.Collections.Generic.IList<double>(MathNet.Numerics.LinearAlgebra.Vector)': user-defined conversions to or from an interface are not allowed    C:\Documents and Settings\czietsman\My Documents\Visual Studio 2008\Math.Net\src\app\MathNet.Iridium\Library\LinearAlgebra\Vector.cs    315    23    Iridium

Is there a reason why CreateNaturalCubicSpline takes an IList as argument instead of a vector or double[?

Thanks for the feedback. I will add a new feature to the tracker for the not-a-knot boundary condition. Beside that there's no detailed interpolation roadmap yet, but I intend to provide additional complex & trigonometric interpolation methods in medium-term.

I decided to use IList<double> because it is the smallest common feature unit we need and because it's directly supported by the two most important structures, double[ ] and List<double>. Btw, there's no need to call "ToList()", simply casting to double[ ] will do the trick.

I think the best solution for vectors would be to make Vector implement IList<double>, too.

The two issues are now tracked as IRID-145 and IRID-146.