Re: [eigen] [PATCH] Toeplitz matrix specialization |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] [PATCH] Toeplitz matrix specialization
- From: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
- Date: Thu, 29 Jan 2009 21:32:24 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=hvcopXTiZVEliNe6hzerQpQ6YhC09sU3D3NGKmvcCY4=; b=o7m2CxRKnfkpn4vnWTdUxrnFXdxeh3aUfL7VtDCBODdRdU7OuB2EAfb/dLPb2H0S73 csdenukMjqz6J4JowchWeB0fS9WCNteWBNeQM7ARNF50lPljdBs3GNVxS3ClJNcavTRk pG3lTqLfZQxPIv0jC5wYZ2G8w3ZDE1X1CQsY4=
- 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=RWYDN9v6B17WdYMu3LQ02kFE0MgwSBRQ1lG6Vf91dUGT3eMWXlX00l/98iWjwAwi64 nL3Fi0olFOCNG3yQ73dAYL1PDXByLQmnSnjGJH3CfE0oPukAMMhOELqX1drN0mMzcTdN pgnTmorxY+xlGjASOMxR+Qu5ImU0NBQFe6pYw=
2009/1/29 Gael Guennebaud <gael.guennebaud@xxxxxxxxx>:
> On Thu, Jan 29, 2009 at 7:55 PM, Keir Mierle <mierle@xxxxxxxxx> wrote:
>> On Thu, Jan 29, 2009 at 6:40 AM, Gael Guennebaud
>> <gael.guennebaud@xxxxxxxxx> wrote:
>>> Hi,
>>>
>>> to start the debate I put some thougths on the wiki:
>>> http://eigen.tuxfamily.org/index.php?title=SpecialMatrix
>>
>> The idea of making solveTriangular into Part::solve() sounds good to
>> me. Right now the hetergeneous API for solving triangular systems is
>> unfortunate. I vote to have solve() work as expected for triangular
>> matrices with the same API as LU::solve, SVD::solve, QR::solve, etc
>> (i.e. MyVec x; bool succeeded = my_triangular_mat.solve(b, &x);).
>> Perhaps mymat.upperTriangular().solve(...)?
>
> yes, exactly.
>
>> Is there an excessive runtime cost to detecting a singular matrix in
>> the triangular solver?
>
> N comparisons, just like for Cholesky.
I don't have strong opinions here, but i'd just like to mention, if we
do changes and the current solveTriangular could become deprecated,
then better mark it as experimental NOW so we can remove it later!!
The time left until the release is useful exactly for that and none of
the projects I feel responsible for are already depending on the
solveTriangular API.
Cheers,
Benoit