|Re: [eigen] compilation failed for not aligned tiny matrix|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] compilation failed for not aligned tiny matrix
- From: WANG Xuewen <xuewen.wang@xxxxxxxxx>
- Date: Wed, 07 Oct 2009 10:02:41 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=sko8q6P0WZU+xcX4BftvXD5LgACtaT+BamwMzjv095s=; b=Psd5w9CEe7QiCUwk/0RAyutMNaL0oKqgEWfMOx+DSTYIE/iYs/ift1TlFt1yboVp0y HMbkQllmGeaWmnHVRFe6xr1FIEVqL/OBPYeIr4CdhizxRxTwS+VuncqJmaFVuWd+PFik lA2A6JdkKREBFzZf29IhfOehXo9MWV7QBgShc=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=sG78hWVv8bmKjkTlxqN8lAcRFdYAYmiGDa3ubJo7K3MvsgV1oBtUvypka0rI3GuOnJ l2f0YZo5ucNq44XARq3Xf1eG01D4ld/B4ntXE4lcvkPGWtac1Nn8zyatSFww3WloghhX D6UiMcTVIi6stEH8A4AlTsvm1SrJjSBWvOaI0=
Benoit Jacob wrote:
It seems that computeInverse is fixed now so I'll use it. Look forward
to have inverse() work in place. Thank you for the work!
2009/10/6 WANG Xuewen <xuewen.wang@xxxxxxxxx>:
Gael Guennebaud wrote:
ok, here the bug is that computeInverse() expect a PlainMatrixType which
in your case is equivalent to TinyRMatrix but without the DontAlign option.
Yes that's a bug in Eigen.
But now, I'm wondering why computeInverse is not a template function ?
Think about submatrices, or, e.g., to perform:
m.transpose().computeInverse(inv); - here m.transpose() is row major and so
computeInverse will expect a row major matrix.
Moreover I'm wondering whether computeInverse() is still useful since we
can make inv = a.inverse() works in place just like compute inverse.
Ah, I didn't try directly inverse() and it does work so I'll change my code
to use inverse. thanks!
This change (making inverse() work in place) isn't implemented yet!
You can use inverse() already but it'll be a few weeks before this is
as efficient as computeInverse.