Hello SAS Community,
I am using the TRAMO/SEATS component of the SAS ETS X13 procedure to attempt to extract the long term trend from a time series. However, SAS combines the trend and cycle together in the output. In getting the trend-cycle, both the trend and cycle would have to be extracted through SEATS but these separate series are not provided in the output. Is there an undocumented option to get this output, or some way to access the working sets prior to the output to grab these series?
It's my first time posting so forgive me if I forget standards, I'm happy to answer any follow up questions if it helps you answer my question.
If it helps, here is my code so far:
proc x13 data=data date=date interval=qtr ; var series; transform function=auto; automdl maxdiff=(1,1) maxorder=(4,1); outlier; seatsdecomp out=output; run;
Thanks,
Sean
Sean,
Here are my thoughts about your question:
WARNING: This is an experimental release of the SEATSDECOMP statement. It has not had the same
level of testing as other components of the SAS system.
Validating code is the most difficult part of the software development process. Often there is little or no software validation done for software that is freely available. The SEATS method in X13 has not yet been validated to our usual standards.
The documentation for the version of SEATS that was used to produce the SEATSDECOMP statement is:
Gómez, V., and Maravall, A. (1997b). Programs TRAMO and SEATS: Instructions for the User, Beta Version. Madrid: Banco de España.
In this document, there are numerous references to splitting the trend and cycle component into different series. However, in examining the printed output from the program, I only see references to a TREND-CYCLE series. In addition, in the SEATS documentation, there are references to output files cycle.t and cyclefac.t. Looking at the files produced by numerous runs of the SEATS FORTRAN program, I only see one file cycle.t, and it is associated with a run that caused a core dump – the program failed to run to completion. This appears to be a situation where the documentation did not accurately describe the features of the software. The fact that the trend cycle was not available in the older version seems to be confirmed by the 2014 article.
Both the EXPAND and TIMESERIES procedure should provide reliable, high quality output. Also, it is easy to output series from one SAS procedure and input the series into another procedure. So, for instance, the B1 series from X13 could be used as input for the TIMESERIES procedure, or the TREND-CYCLE component could be used as input to the EXPAND procedure.
Thank you for supplying your data. We will add the data to our test validation code for the X13 procedure. If you have any further questions, please let me know.
Hi Sean,
I am looking in to this. It would be helpful to have your data.
Thanks.
Hey Tammy,
I've been using the Australian Bureau of Statistic's employment by industry release, specifically for Agriculture, Forestry and Fishing and its child series Agriculture. I've attached my data set of the two quarterly raw series.
I also found this update notes to TRAMO/SEATS that talks about the decomposition of the trend-cycle into its business cycle and long-term trend components. Maybe this feature is not yet available in the SAS X-13 package.
Sean
Sean,
Here are my thoughts about your question:
WARNING: This is an experimental release of the SEATSDECOMP statement. It has not had the same
level of testing as other components of the SAS system.
Validating code is the most difficult part of the software development process. Often there is little or no software validation done for software that is freely available. The SEATS method in X13 has not yet been validated to our usual standards.
The documentation for the version of SEATS that was used to produce the SEATSDECOMP statement is:
Gómez, V., and Maravall, A. (1997b). Programs TRAMO and SEATS: Instructions for the User, Beta Version. Madrid: Banco de España.
In this document, there are numerous references to splitting the trend and cycle component into different series. However, in examining the printed output from the program, I only see references to a TREND-CYCLE series. In addition, in the SEATS documentation, there are references to output files cycle.t and cyclefac.t. Looking at the files produced by numerous runs of the SEATS FORTRAN program, I only see one file cycle.t, and it is associated with a run that caused a core dump – the program failed to run to completion. This appears to be a situation where the documentation did not accurately describe the features of the software. The fact that the trend cycle was not available in the older version seems to be confirmed by the 2014 article.
Both the EXPAND and TIMESERIES procedure should provide reliable, high quality output. Also, it is easy to output series from one SAS procedure and input the series into another procedure. So, for instance, the B1 series from X13 could be used as input for the TIMESERIES procedure, or the TREND-CYCLE component could be used as input to the EXPAND procedure.
Thank you for supplying your data. We will add the data to our test validation code for the X13 procedure. If you have any further questions, please let me know.
Join us for SAS Innovate 2025, our biggest and most exciting global event of the year, in Orlando, FL, from May 6-9. Sign up by March 14 for just $795.
Learn how to run multiple linear regression models with and without interactions, presented by SAS user Alex Chaplin.
Find more tutorials on the SAS Users YouTube channel.