Summary: | Public BandMatrix functionality wish list | ||
---|---|---|---|
Product: | Eigen | Reporter: | Rhys Ulerich <rhys.ulerich> |
Component: | General | Assignee: | Nobody <eigen.nobody> |
Status: | NEW --- | ||
Severity: | enhancement | CC: | gael.guennebaud, jacob.benoit.1 |
Priority: | --- | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Rhys Ulerich
2011-03-24 05:10:41 UTC
Hi, all your requests are obviously planed. To reach these goals, the next step is to introduce the notion of "range vector" which is a column (or a row) where the nonzeros are known to be inside a given range. Then everything should be fairly easy to implement. Actually, the most tricky part is probably: BandMatrix3 = alpha * BandMatrix1 + beta * BandMatrix2; which have to be implemented as: 1 - allocate space in BandMatrix3 and set it to zero 2 - BandMatrix3 += alpha * BandMatrix1 3 - BandMatrix3 += beta * BandMatrix2 With the work in progress refactoring of our expression tree and evaluation mechanism, such an evaluation of BandMatrix3 = alpha * BandMatrix1 + beta * BandMatrix2; should become possible. -- 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/233. |