Confirmed! Allin is the best!!!

[helio@localhost temp]$ ./test
197 number of observations: 62789
198 number of observations: 52313
199 number of observations: 50733
200 number of observations: 50762
201 number of observations: 51009
202 number of observations: 50944
203 number of observations: 51234
[helio@localhost temp]$ ./test
197 number of observations: 63529
198 number of observations: 51731
199 number of observations: 49764
200 number of observations: 49832
201 number of observations: 50216
202 number of observations: 51201
203 number of observations: 50682



On Wed, Apr 16, 2014 at 12:13 PM, Allin Cottrell <cottrell@wfu.edu> wrote:
On Wed, 16 Apr 2014, GOO Creations wrote:

> Thanks Helio. So it's not just me.
>
> Since the mathematics behind Mahalanobis indicate a linear dependency between
> the observation count and the execution time, I'm simply going to ignore this
> time-jump.

I've found the cause of the time-jump. It has nothing to do with the
actual Mahalanobis calculations and is purely to do with the apparatus for
printing the results, which up till now has been interleaved with the
computation (but is now separated in CVS).

The point is that we do certain calculations designed to ensure a
reasonably "pretty" printout, but once the sample size exceeds a certain
size we switch to a less rigorous but cheaper variant of that code. Since
your test program passes a NULL pointer for the printing there's actually
no call to run any of the prettification code, and in CVS we no longer do
so.

Allin Cottrell
_______________________________________________
Gretl-users mailing list
Gretl-users@lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-users