Re: [eigen] In-place decompositions; was: UmfPackSupport vs SuperLUSupport: input matrix |

[ Thread Index | Date Index | More lists.tuxfamily.org/eigen Archives ]

*To*: eigen@xxxxxxxxxxxxxxxxxxx*Subject*: Re: [eigen] In-place decompositions; was: UmfPackSupport vs SuperLUSupport: input matrix*From*: Christoph Hertzberg <chtz@xxxxxxxxxxxxxxxxxxxxxxxx>*Date*: Fri, 22 Nov 2013 13:37:31 +0100

On 16.04.2013 17:50, Gael Guennebaud wrote:

On Tue, Apr 16, 2013 at 3:49 PM, Christoph Hertzberg <chtz@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:A fixed-size use case I would have is to have a lot of rather small fixed size matrices which are accumulated simultaneously and shall all be decomposed, once the accumulation is done.damn, I was not expecting use cases for small fixed size matrices, but yours is perfectly reasonable. Then there are two approaches, either the factorization uses the memory shared by the matrix A, or we create

I just filed a feature request for this: http://eigen.tuxfamily.org/bz/show_bug.cgi?id=707 API-wise this could be accomplished by declaring the decomposition as Decomposition<Ref<MatrixXd> >.

Christoph -- ---------------------------------------------- Dipl.-Inf., Dipl.-Math. Christoph Hertzberg Cartesium 0.049 Universität Bremen Enrique-Schmidt-Straße 5 28359 Bremen Tel: +49 (421) 218-64252 ----------------------------------------------

**Follow-Ups**:**[eigen] Unexpected behavior with rowwise().reverse()***From:*Rob Conde

**Messages sorted by:**[ date | thread ]- Prev by Date:
**Re: [eigen] Assigning a dynamic matrix to a fixed size matrix const reference causes invalid read** - Next by Date:
**[eigen] Unexpected behavior with rowwise().reverse()** - Previous by thread:
**Re: [eigen] Assigning a dynamic matrix to a fixed size matrix const reference causes invalid read** - Next by thread:
**[eigen] Unexpected behavior with rowwise().reverse()**

Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |