|[eigen] Eigen 3.2-beta1 ??|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen <eigen@xxxxxxxxxxxxxxxxxxx>
- Subject: [eigen] Eigen 3.2-beta1 ??
- From: Gael Guennebaud <gael.guennebaud@xxxxxxxxx>
- Date: Fri, 22 Feb 2013 16:11:36 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=XDctujl4Tdr6E2Nwc6QKYF7XbqPHr1iV7ukhbG2HidI=; b=FF1+itmqneGfmkMyJIffRVYFvZNnGxwScSXrhPHyFAsUZQuJmI2AHKjLPzR+jirX+k /C8SiEZANvuotKgZ5kVt8OpoQEB/IZYMWORLJaCD58WPA+0wIcJn7k9XOccDrIYAyZF6 P/+o1Ffz4jayRDkPgIDPcu+fvoThd2H6mGw98mj9JvPxXRFlqPuIY7IL4d3QdW0h+Vm+ KsG78DclYvwySYj78k4sVXcJYUedoClzTGYDxcJk4gtI8BrE82gt6p06llrJgRFNrSNO qLrj1228jTZ8lCnb4R8wSYPRPRIZCVVG2olpObt2QPlElPakjZfS5GEVrHBMc7oH+owM 0mOw==
I know that none of the major features initially planed for 3.2 are
here (evaluators, indexed sub-matrices, AVX) but 1) it has been 8
months since 3.1, and 2) the devel branch already contains many new
cool and very useful features that, from my point of view, justify a
new release of Eigen. Here is a short list of them:
- Core: The Ref<> class allowing to write non templated function
taking various kind of Eigen dense objects without copies.
- Eigenvalues: RealQZ factorization and GeneralizedEigenSolver
- SparseLU: built-in sparse LU with super-nodes and numerical column pivoting.
- SparseQR: rank-revealing sparse QR factorization (numerical column pivoting).
- OrderingMethods: extended with COLAMD and a unified Ordering API.
- MetisSupport: wrapper to the famous graph partitioning library.
- SPQRSupport: wrapper to suitesparse's supernodal QR solver.
- plus many other small improvements and fixes that could not be backported.
So I think we should make beta release asap. To give us the time to
agree on this and on the list of features that should or not make it,
as well as to perform the necessary API reviews, I propose to schedule
the release on Tuesday 5th of March. During this period everybody is
- discuss this release plan in general (timing, features that should
make it, etc.)
- review the APIs and documentations of these new features (very important)
- help identifying regressions by running the unit tests on exotic
platforms or even testing our code against the devel branch
- and of course documentation and fix patches are always welcome !
I'll start the discussion by saying that in the above list I'm tempted
to move MetisSupport and SPQRSupport in unsupported/ because I
realized that maintaining such wrappers to externals libraries is
pretty time consuming on the long run.