Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Minor enhancements to custom LDLT implementations #489
Minor enhancements to custom LDLT implementations #489
Changes from all commits
2b48438
e0ba89c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There must be a way to do this via Eigen types such that if the input is static sized the output will be too?
Eigen::Matrix<_Scalar, _Rows, _Cols>
would have allowed for that, butEigen::MatrixXd
will force all output to be dynamic doubles. I don't think it's a problem for us, and feel free to proceed without changing this, it just feels like there should be a way,Eigen::DenseBase<Derived>::PlainMatrix
or something like that?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the problem is not all expression types involved here derive from even
DenseBase
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MatrixBase
inherits fromDenseBase
so it should right? https://gitlab.com/libeigen/eigen/-/blob/master/Eigen/src/Core/MatrixBase.h#L52There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but this gets used with things other than a
MatrixBase
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I meant that if the input argument is a
MatrixBase<Derived>
then maybe you could get thePlainMatrix
from it?I doubt this would work but if
Eigen::MatrixBase<Derived>
works, thenEigen::DenseBase<Derived>
should right?Anyway everytime I dig into Eigen I start to think I understand how to extend it, then I find something like
Solve.h
and get thoroughly lost. This isn't important enough to spend the time figuring it out.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry . . . I think the long-term "right way" is to make our
solve()
members look just like Eigen's ones and only overload_solve_impl()
or whatever it is that takes anRhsType
reference.