| Re: [eigen] RotationBase times DiagonalMatrix |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] RotationBase times DiagonalMatrix
- From: Hauke Heibel <hauke.heibel@xxxxxxxxxxxxxx>
- Date: Mon, 26 Sep 2011 09:05:46 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=YBnO81z69YKttVissa7r/Ca8n76lsjLtNKlSfyuwiTE=; b=xotGqmNO/ZhlMAcFWCVeKBF+3WCoyH87aEtN+wGHQNLhqefX6fl9SnhVP3QE8V/Bdm 2EFrvU9VI1XgxyJXbd77E6YRBAIw4OvOhUbF8wFT/D7H3+Xx3RxHORvDeOBUon0JOxSw g8ZMMjFSqTrH4+C7j1p6ziiqg0tK5z5XMvxA0=
On Sat, Sep 24, 2011 at 4:47 PM, Christoph Hertzberg
<chtz@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> I guess you meant Dim*(Dim+1). Besides the memory maybe also important is
> the increased number of flops: 2n²+n for Transform, vs. n for
> Translate/Scale.
Yes, of course. That's also an issue.
> Maybe introducing a
>
> template<class Derived>
> class TransformBase;
>
> is the solution. This would describe all Transformations -- affine or pure
> linear.
Probably the optimal solution. It just takes some time to implement
such a change.
> If then someone does:
>
> Transform a = Translation(...);
>
> he'll get a performance/memory penalty, but that's exactly the same for
>
> Matrix<..> m = Diagonal<...>(...);
We would already have this scenario, when we removed the explicit
keywords, right?
- Hauke