Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

selfadjointView may be a bottle neck #638

Open
jcarpent opened this issue Dec 3, 2019 · 3 comments
Open

selfadjointView may be a bottle neck #638

jcarpent opened this issue Dec 3, 2019 · 3 comments

Comments

@jcarpent
Copy link
Member

jcarpent commented Dec 3, 2019

d->Fx.bottomRightCorner(nv, nv).noalias() = a_partial_dtau * d->pinocchio.M.selfadjointView<Eigen::Upper>();

From my knowledge of Eigen, selfadjointView may lead to slow computations. It may be better to fill the entire mass matrix M and then performing the dense computations.

@cmastalli
Copy link
Member

Thanks for the feedback. I will benchmark it asap!

@cmastalli cmastalli added this to open in Feature extension Dec 3, 2019
@cmastalli
Copy link
Member

@proyan you might want to handle this issue.

@cmastalli
Copy link
Member

@jcarpent --- could I ask you (in your experience) when we should use selfadjointview (i.e., with which matrix dimension)?

As described here (https://stackoverflow.com/questions/39606224/does-eigen-have-self-transpose-multiply-optimization-like-h-transposeh), selfadjointview is not useful for small matrices. But it is not clear (in this post) what matrix dimensions are considered small

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants