|Re: [eigen] Permuted Matrix|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] Permuted Matrix
- From: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
- Date: Mon, 19 Jul 2010 18:30:34 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=XeNwzmL37QZ5af1hlNA4uJ7XC7af3YhW6l8auwVJ56o=; b=e8HRR0mvzFZRLyuuc+gHCDS6FhLPvu2ZPCJ0bP7+EbLwpLAFM72rska2D8igSrChgy WDTQEYnZUzrlccVfLsXVqiTVgbJebMgWkAQrfS65EeNt9PMdKULRtGG44EPHow7KjV6M 7BI7aWtHM1p8LEuR9ZwhYG37zlH5NhrRoSDkY=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=VR0Bz4qGzFh2XfsHuiHzxB03CwerVd+6jEXvH+ISTv1F6EnSW0whXoUVq3bFfftQkw gk1S4lD4FWg4TwfXZQ3pHKY3PgVN7csBkeLstQNvn//TAwH/XQ+P7gGHjTM7X4EYijai UjvxZmjyXBwS/YxVEBnDWcLpnWAzv5x8xQHp8=
You're not missing anything, actually you understood everything very
well. You really hit a limitation in our design here. Expressions are
either DirectAccess, which assumes a simple memory layout, or have no
write support at all. There's no middle ground. These two cases
correspond to the two cases in DenseCoeffsBase, as you found out.
The fix is to add a third case in DenseCoeffsBase, in between the two
existing cases in the inheritance diagram. The three cases could be
called respectively, "direct access", "lvalue without direct access",
"rvalue-only". Or something like that.
Fortunately for us, this is something completely internal so we can
fix it later --- so please understand if I don't have much motivation
to do it right now :) Feel free to send a patch though.
2010/7/19 ESCANDE Adrien 222264 <adrien.escande@xxxxxx>:
> I'd like to implement a permuted matrix i.e. a matrix P base on another M, such as P(i,j) = M(r[i], c[j]) for some permutation vectors r and c. It is very similar to the subject of another thread (how to create a "virtual" array or matrix) whose conclusion was to look at the way Minor class is implemented.
> Based on this Minor example, it is indeed easy to implement a PermutedMatrix class for read-only purpose. It goes like this:
> template<typename MatrixType> class PermutedMatrix
> : public MatrixBase<PermutedMatrix<MatrixType> >
> overload of coeff and coeffRef
> One can then access to coefficients of the matrix, use block expression, triangular view,...
> Writing in such a matrix is however a problem: PermutedMatrix can't have the DirectAccessBit bit because the "layout of the array of coefficients" is not "exactly the natural one suggested by rows(), cols(), outerStride(), innerStride(), and the RowMajorBit" DirectAccessBit documentation).
> Thus PermutedMatrix only derives from DenseCoeffsBase<Derived, false> and not DenseCoeffsBase<Derived, true>. In particular, it does not inherit the good operator() (Index, Index), and the copyCoeffByOuterInner(Index, Index, const DenseBase<OtherDerived>&) methods, the latter being needed in the assignation.
> Adding these missing methods directly in PermutedMatrix solves part of the problem: one can do P(i,j) = some_value or P = some_matrix, but they are still missing in expression based on PermutedMatrix , thus one can not do P.block(i,j,r,c) = another_matrix, because the copyCoeffByOuterInner of DenseCoeffsBase<Expr<PermutedMatrix<MatrixType> > > (in my example, Expr is Block) is not correctly defined.
> Do I miss something on this problem ? Any direction I could take, or flag I don't know of ? I'm not very familiar with Eigen internals yet, so any pointers would be welcome.
> Thank you,
> Adrien Escande