|Summary:||Tests : precision-oriented tests|
|Product:||Eigen||Reporter:||Benoit Jacob <jacob.benoit.1>|
|Bug Depends on:|
Description Benoit Jacob 2010-10-16 04:49:00 UTC
Most of our current tests only check for rough sanity of the result, we need precision-oriented tests too. Since it's impossible to predict what the precision of a computation should be in general, one should manually record precision at a time when the algorithm is known to be sane, and make that the benchmark to check against, to prevent future regressions. Another approach is to compare precision to other existing libraries, but then, probably only some LAPACK libs are reliable enough for that. Also notice that if the "LAPACK test suite" todo item (bug 63) is achieved, it will already guarantee precision quite nicely, making this todo item less of an emergency.
Comment 1 Gael Guennebaud 2015-06-16 19:43:04 UTC
The situation has already been significantly improved. In particular, SVD and selfadjoint-eigenvalues unit tests are now pretty aggressive in terms of numerical robustness. In the future it would be nice to extend the approach taken for SVD to other decompositions. For sparse problems, we check the accuracy on a set of real-world problems. Still need to extend this set and automate its usage. Good enough for 3.3.
Comment 2 Gael Guennebaud 2018-10-09 07:47:39 UTC
Comment 3 Nobody 2019-12-04 09:43:12 UTC
-- GitLab Migration Automatic Message -- This bug has been migrated to gitlab.com's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.com/libeigen/eigen/issues/64.