Dear Eigen developers and users,

Hauke Heibel has written spline extensions for Eigen, see also
http://bitbucket.org/hauke/eigen_splines/. Thank you for this!

Unfortunately, this is a fork of the full Eigen library with his spline extension. Why is it necessary to fork all of the library? Are there any extensions or changes in the core part of Eigen necessary? I would dislike to use both versions of Eigen in the same code. But, I would like to use the latest version of the Eigen main library.

On the bitbucket fork comparison page http://bitbucket.org/hauke/eigen_splines/compare/..eigen/eigen I learned that I can merge back in the changes done in the spline variant of Eigen. But how does this affect the Eigen core part?

Unfortunately, I could not find any information on this on the webpage on the variant with the spline tools. I think this unnecessarily complicates the use of the spline functions with the main branch of the Eigen library.

Furthermore, why is the spline extension not included in the main version of Eigen, maybe first as an "unsupported" extension? I think, this would help the spline extension to be known by Eigen users and could be an important argument for users to use Eigen at all.

Thank you!

Hi kbr,

thanks for your interested in the spline code. I have recently adapted it to the most recent Eigen trunk, but I am not maintaining the fork anymore. The old code of the fork also contained quite a few bugs and I have not yet been able to write many unit tests.

My current version seems to be working fine and I also integrated an interpolating spline fitting based on Eigen::HouseholderQR including the required functions for knot averaging and a simple chord length parameterization.

I would love to move this stuff to the unsupported module because I think that a joined effort in extending such a module would be really great.

Even though I have write access to Eigen, I am not sure about adding the code to the unsupported module right away. What I most probably could do is to update the fork such that everything is in the unsupported module and then fix the remaining design issues before merging the fork and the main branch.

If Gael, Benoit and other people who are interested in the module would help me with feedback after the integration I could do that but otherwise my time is too scarce to update the fork without good reason.

- Hauke