You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for publishing this library! I gave it a try in a project of mine, and while it works great, I was wondering if it would make sense to expose the Eigen Matrix type to callers, ie. make it a template typename.
I'm using least squares to solve an objective in which the Jacobian is sparse (mostly zeros), and Eigen has SparseMatrix implementations for decompositions and solvers (see eg. SparseQR), which might be more efficient/fast than the default dense matrix ones. I must admit I haven't benchmarked performance, but figured you should be aware.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi,
Thanks for publishing this library! I gave it a try in a project of mine, and while it works great, I was wondering if it would make sense to expose the Eigen
Matrix
type to callers, ie. make it a template typename.I'm using least squares to solve an objective in which the Jacobian is sparse (mostly zeros), and Eigen has
SparseMatrix
implementations for decompositions and solvers (see eg.SparseQR
), which might be more efficient/fast than the default dense matrix ones. I must admit I haven't benchmarked performance, but figured you should be aware.Thanks.
The text was updated successfully, but these errors were encountered: