Re: [Gretl-users] problem with simulation loop times
Am 10.02.2008 12:38, Riccardo (Jack) Lucchetti schrieb:
On Sun, 10 Feb 2008, Sven Schreiber wrote:
> One guess is that the huge script text output may be responsible
for
> part of the problem -- here it would help if a VECM could be estimated
> without any output, as I was suggesting in a previous email (vecm with
> the --silent option).
On linux, you have a poor man's version of the --quiet switch, that is
redirecting output to /dev/null, as in
outfile "/dev/null" --write
vecm 2 3 1 2 3
outfile "/dev/null" --close
I don't know if anything similar exists on Windows.
Well luck has it that I'm currently working on Linux again, and your
idea was brilliant -- the time for 500 runs is down from 71 to 17, and
for 1000 runs from 257 to 35, so now it's linear as expected! Thanks a
lot for solving this problem!
(BTW, I had to put the 'outfile "/dev/null" --write' command right into
the function where the 'vecm' command is; it wouldn't work to wrap the
top-level function call in it. It smells like a little bug to me, but
I'm not sure.)
three cheers for Jack :-)
sven