On 30 May 2011, Terrance Savitsky wrote:
> Hello, After upgrading to the 0.2.21 release of RcppArmadillo, my
> previously working code (across many functions) ceased working (on a
> Windows XP installation). I re-installed the previous version (0.2.20)
> from CRAN (via a server location not yet up
On 31 May 2011 05:02, Savitsky, Terrance wrote:
> Dr. Sanderson, I've been able to verify that my issue resides in the
> inv() function (that I typically apply to small p x p matrices, where p
> = 3 - 10). In particular, the new version/algorithm induces numerical
> instability.
This is a bit st
Hi Baptiste,
Thanks for the bug report. I'll take a look at the underlying issues.
On 31 May 2011 09:48, baptiste auguie wrote:
> Sorry, I had too many spaces in the vectors. The conclusion is the same
> though.
>
> library(inline)
> require( RcppArmadillo )
>
> ## let's calculate this produc
k if
there is a problem in inv().
In the meantime I recommend sticking to the previous version of
Armadillo and RcppArmadillo.
btw, for dot products I recommend using the dot() and cdot() functions
-- they're generally faster than going through the multiplication
operator.
On 31 May 2011 11:39
s,
Conrad
On 1 June 2011 05:58, baptiste auguie wrote:
> Thanks so much, Conrad!
>
> Best regards,
>
> Baptiste
>
> On 31 May 2011 23:37, Conrad Sand wrote:
>> I've found the cause of the issue (involves handling of small matrices).
>>
>> The fix is eas
For tiny matrices (ie. <= 4x4), Armadillo by default uses fast
algorithms for det(), inv() and solve().
In rare instances these fast algorithms may not be as precise as the
standard algorithms found in Lapack.
As such, in the updated version of Armadillo I've added an option to
det(), inv() and s
Hi everyone,
I've just released Armadillo 1.99.5, which is likely to get wrapped up
in the next release of RcppArmadillo.
See http://arma.sourceforge.net/
The 1.99.x series are beta releases for the upcoming 2.0 release.
There are a few minor but important API changes and additions in
1.99.5, el
I believe this is an issue in Clang, not Armadillo. There is another
problem with Clang: it tends to be overly picky, to the point of doing
implicit template instantiations (where no instantiation was
requested!).
The over-pickiness broke the static assertion approach used in
Armadillo, which work
