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.
Thanks for all the help.
Regards
Chris
On 2014/04/16 12:51 PM, Hélio Guilherme wrote:
Hello,
These are my results:
On Fedora 19.0 x64 4 core
[helio@localhost temp]$ ./test
197 number of observations: 707623
198 number of observations: 675847
199 number of observations: 679392
200 number of observations: 557697
201 number of observations: 536804
202 number of observations: 578269
203 number of observations: 544649
[helio@localhost temp]$ ./test
197 number of observations: 777980
198 number of observations: 764587
199 number of observations: 770005
200 number of observations: 623716
201 number of observations: 627000
202 number of observations: 630206
203 number of observations: 634468
[helio@localhost temp]$ ./test
197 number of observations: 695839
198 number of observations: 678020
199 number of observations: 681358
200 number of observations: 534876
201 number of observations: 537547
202 number of observations: 539711
203 number of observations: 543831
[helio@localhost temp]$ ./test
197 number of observations: 709759
198 number of observations: 684160
199 number of observations: 685812
200 number of observations: 534485
201 number of observations: 537334
202 number of observations: 573589
203 number of observations: 543497
On OpenSUSE 13.1 x64 2 core
helio@linux-techno:~> ./test
197 number of observations: 1060657
198 number of observations: 1097359
199 number of observations: 1104009
200 number of observations: 867470
201 number of observations: 872487
202 number of observations: 874292
203 number of observations: 881876
helio@linux-techno:~> ./test
197 number of observations: 730982
198 number of observations: 732811
199 number of observations: 736721
200 number of observations: 579397
201 number of observations: 584108
202 number of observations: 584735
203 number of observations: 588359
helio@linux-techno:~> ./test
197 number of observations: 731426
198 number of observations: 738590
199 number of observations: 741741
200 number of observations: 583523
201 number of observations: 584833
202 number of observations: 588973
203 number of observations: 592129
helio@linux-techno:~> ./test
197 number of observations: 730169
198 number of observations: 732672
199 number of observations: 737452
200 number of observations: 579829
201 number of observations: 583927
202 number of observations: 584652
203 number of observations: 589383
As you can see the time-jump also happens here. Note the high 1st run
times on OpenSUSE.
On Tue, Apr 15, 2014 at 4:49 PM, GOO Creations <goocreations(a)gmail.com
<mailto:goocreations@gmail.com>> wrote:
...
I've attached a small example program (with a makefile) that does
the test. I'm using gettimeofday, which will probably only work
under Linux. It might take a couple of seconds to execute. I would
apprciate it if someone could run it (sorry Allin, this is
probably the wrong mailing list again for posting C code), and
verify that I'm not the only one with this time-jump.
These are my outputs:
/197 number of observations: 784814//
//198 number of observations: 760379//
//199 number of observations: 759822//
//200 number of observations: 598327//
//201 number of observations: 602174//
//202 number of observations: 604390//
//203 number of observations: 607213//
/
Chris
_______________________________________________
Gretl-users mailing list
Gretl-users(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-users