Nope I agree -it was just a look see exercise as a VAR as there might have
been some feedback in the system between the 2 variables. Back to ARMAX
univariate specifications..
AT least I have pointed out an issue that is replicable.
cheers
Brian
On Sun, 20 Dec 2020 at 15:44, Sven Schreiber <svetosch(a)gmx.net> wrote:
Am 20.12.2020 um 16:34 schrieb Brian Revell:
Hi Sven
the specification was just pushing data and parameters to their limits
with specific lags of 1 3 6 and 9 years specified in the 2 dependent
variables to try to pick up some cyclical elements in the data and with
only 22 observations. I will try it dropping the lag 9 later (I have other
ARMAX results I don't want to risk losing at present until I have finished
the session) to see if it makes the difference between crash or go!
Windows 10 OS. However, i would have expected some failure messages, not a
complete crash.
Brian
Thanks, that's already enough - I can confirm the crash here on Windows
with the latest snapshot (with 22 obs and using the GUI to enter the lag
choice "1,3,6,9", without the quotes).
Of course, with a max lag of 9 you only have 13 effective obs left and
that is just barely enough to estimate 4*2 + 2 = 10 parameters in each
equation. Nonetheless, in theory it should still work (although I wouldn't
recommend it econometrically), and needless to say a crash is never
acceptable.
I suspect that the fix will be relatively easy (for Allin, that is ;-)
cheers
sven
_______________________________________________
Gretl-users mailing list -- gretl-users(a)gretlml.univpm.it
To unsubscribe send an email to gretl-users-leave(a)gretlml.univpm.it
Website:
https://gretlml.univpm.it/postorius/lists/gretl-users.gretlml.univpm.it/