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