Page 1 of 1
x12 specification file
Posted: Fri Apr 04, 2014 10:05 am
by HollEviews
Please do you have an example of a specification file that runs through the x12 command? I am trying to run an x12 seasonal adjustment using the "force{}" option, so for example:
cvnsa.x12(sfile=c:\testx12.spc) cvsatot1
but I keep getting an error message saying that the file testx12 cannot be found. The contents of testx12.spc is simply:
force{lambda=1, rho=0.85, type = regress, save = saa}
Any suggestions would be greatly appreciated.
many thanks!
Re: x12 specification file
Posted: Fri Apr 04, 2014 10:33 am
by EViews Gareth
Try putting it somewhere other than the root of C:
Re: x12 specification file
Posted: Mon Apr 07, 2014 7:03 am
by HollEviews
Many thanks for the very quick and helpful replies. It turned out that my text editor was adding a "txt" at the end of my file name, so it wasn't found.
One follow-on question to this. I have managed to get Eviews to call the x13 programme and create the series that I'm after, but I can't figure out how to read that series back into Eviews. I have used the following:
cvnsa.x13(spec=satest1)
Where satest1 is a text object:
series{
title = "CVNSA"
start = 1997.1
period = 4
modelspan = (1997.01, 2013.04)
name = "CVNSA"
file = "C:\AppData\ev_temp\EVX13TMP.DAT"
decimals = 1
}
transform{
function = log
}
force{
type = regress
save = saa
}
x11{
save = (d11)
}
A file called evx13tmp.saa is created, and this holds the dataseries that I want. Is there an easy way to read this into Eviews?
Thank you!!
Re: x12 specification file
Posted: Mon Apr 07, 2014 7:45 am
by EViews Gareth
I guess just use wfopen to open it.
Re: x12 specification file
Posted: Sat Nov 21, 2015 12:59 pm
by xprimexinverse
Hi, HollEviews.
I've attached a subroutine that handles both the force option as well as automatic reading of the .saa file.
The key to this is really just to use @temppath to locate the .saa file. Once you have the file's location, an import statement can load the data into the workfile for you.
See the attached program to see what this looks like. Both Quarterly and Monthly variations of the import statement are handled.
Cheers,
Graeme