<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: proc ARIMA to identify optimal lag in SAS Forecasting and Econometrics</title>
    <link>https://communities.sas.com/t5/SAS-Forecasting-and-Econometrics/proc-ARIMA-to-identify-optimal-lag/m-p/680485#M3947</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/313878"&gt;@Golf&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The difference in the results returned by the MINIC option in your two PROC ARIMA steps&amp;nbsp;&lt;SPAN style="font-family: inherit;"&gt;is due to a difference in the approximation used for the error series.&amp;nbsp; In the first PROC ARIMA step, the error series model was an AR(12) model, whereas in the second PROC ARIMA step, the error series model was an AR(15) model.&amp;nbsp; If you include the PERROR= option with the same specification in both IDENTIFY statements, then the Minimum Information Criterion values will the the same through AR lag 12.&amp;nbsp; For example:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;proc arima data = ARDL;
identify var = dnpl MINIC p=(1:12) q=0 perror=(10:12);
identify var = dnpl MINIC p=(1:15) q=0 perror=(10:12);
run;&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;Regarding your question on how to "add intercept and trend to this procedure", I assume you mean to the underlying procedure used by the MINIC option.&amp;nbsp; The methodology used by the MINIC option automatically corrects for the mean, however, it assumes the series is stationary (ie. constant mean and variance).&amp;nbsp; If your series is non-stationary, then you can include a differencing specification in the VAR= option to detrend the series.&amp;nbsp; The MINIC option operates on the differenced series.&amp;nbsp; If your series has a deterministic trend component, then you will need to detrend the series prior to running PROC ARIMA with the MINIC option.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;For more information on the MINIC option, please see the following documentation link:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;&lt;A href="https://go.documentation.sas.com/?docsetId=etsug&amp;amp;docsetTarget=etsug_arima_details05.htm&amp;amp;docsetVersion=15.1&amp;amp;locale=en" target="_self"&gt;https://go.documentation.sas.com/?docsetId=etsug&amp;amp;docsetTarget=etsug_arima_details05.htm&amp;amp;docsetVersion=15.1&amp;amp;locale=en&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;I hope this helps!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;DW&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 31 Aug 2020 17:07:40 GMT</pubDate>
    <dc:creator>dw_sas</dc:creator>
    <dc:date>2020-08-31T17:07:40Z</dc:date>
    <item>
      <title>proc ARIMA to identify optimal lag</title>
      <link>https://communities.sas.com/t5/SAS-Forecasting-and-Econometrics/proc-ARIMA-to-identify-optimal-lag/m-p/646950#M3943</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;I have 2 questions about proc ARIMA.&amp;nbsp; &amp;nbsp;I hope somebody can help me out.&lt;/P&gt;
&lt;P&gt;(1)&amp;nbsp; I have tried to find optimal lag length of ARMA process by using&amp;nbsp; procedure (a) and (b)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Why the minimum information criterion changing when we change p in proc ARIMA?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;&lt;U&gt; Procedure (a)&lt;/U&gt; :&amp;nbsp; &amp;nbsp;p = 1, 2, ..., 12&amp;nbsp; &amp;nbsp; &amp;nbsp;-&amp;gt; This lead to indicate 12 as optimal lag.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Golf_0-1589252416587.png" style="width: 999px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/39317i9EC65150C334E065/image-size/large?v=v2&amp;amp;px=999" role="button" title="Golf_0-1589252416587.png" alt="Golf_0-1589252416587.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;&lt;U&gt; Procedure (b)&lt;/U&gt; :&amp;nbsp; &amp;nbsp;p = 1, 2, ..., 12&amp;nbsp;&amp;nbsp;-&amp;gt; This lead to indicate 10 as optimal lag.&lt;/P&gt;
&lt;DIV id="tinyMceEditorGolf_4" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Capture.PNG" style="width: 999px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/39321i981AA340C377EAA7/image-size/large?v=v2&amp;amp;px=999" role="button" title="Capture.PNG" alt="Capture.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;(2)&amp;nbsp; How Can I add intercept and&amp;nbsp; trend in this procedure?&lt;/P&gt;
&lt;P&gt;Thank You.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 May 2020 03:13:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Forecasting-and-Econometrics/proc-ARIMA-to-identify-optimal-lag/m-p/646950#M3943</guid>
      <dc:creator>Golf</dc:creator>
      <dc:date>2020-05-12T03:13:06Z</dc:date>
    </item>
    <item>
      <title>Re: proc ARIMA to identify optimal lag</title>
      <link>https://communities.sas.com/t5/SAS-Forecasting-and-Econometrics/proc-ARIMA-to-identify-optimal-lag/m-p/680485#M3947</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/313878"&gt;@Golf&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The difference in the results returned by the MINIC option in your two PROC ARIMA steps&amp;nbsp;&lt;SPAN style="font-family: inherit;"&gt;is due to a difference in the approximation used for the error series.&amp;nbsp; In the first PROC ARIMA step, the error series model was an AR(12) model, whereas in the second PROC ARIMA step, the error series model was an AR(15) model.&amp;nbsp; If you include the PERROR= option with the same specification in both IDENTIFY statements, then the Minimum Information Criterion values will the the same through AR lag 12.&amp;nbsp; For example:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;proc arima data = ARDL;
identify var = dnpl MINIC p=(1:12) q=0 perror=(10:12);
identify var = dnpl MINIC p=(1:15) q=0 perror=(10:12);
run;&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;Regarding your question on how to "add intercept and trend to this procedure", I assume you mean to the underlying procedure used by the MINIC option.&amp;nbsp; The methodology used by the MINIC option automatically corrects for the mean, however, it assumes the series is stationary (ie. constant mean and variance).&amp;nbsp; If your series is non-stationary, then you can include a differencing specification in the VAR= option to detrend the series.&amp;nbsp; The MINIC option operates on the differenced series.&amp;nbsp; If your series has a deterministic trend component, then you will need to detrend the series prior to running PROC ARIMA with the MINIC option.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;For more information on the MINIC option, please see the following documentation link:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;&lt;A href="https://go.documentation.sas.com/?docsetId=etsug&amp;amp;docsetTarget=etsug_arima_details05.htm&amp;amp;docsetVersion=15.1&amp;amp;locale=en" target="_self"&gt;https://go.documentation.sas.com/?docsetId=etsug&amp;amp;docsetTarget=etsug_arima_details05.htm&amp;amp;docsetVersion=15.1&amp;amp;locale=en&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;I hope this helps!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-family: inherit;"&gt;DW&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Aug 2020 17:07:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Forecasting-and-Econometrics/proc-ARIMA-to-identify-optimal-lag/m-p/680485#M3947</guid>
      <dc:creator>dw_sas</dc:creator>
      <dc:date>2020-08-31T17:07:40Z</dc:date>
    </item>
    <item>
      <title>Re: proc ARIMA to identify optimal lag</title>
      <link>https://communities.sas.com/t5/SAS-Forecasting-and-Econometrics/proc-ARIMA-to-identify-optimal-lag/m-p/680582#M3949</link>
      <description>Thank You so much.</description>
      <pubDate>Tue, 01 Sep 2020 00:21:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Forecasting-and-Econometrics/proc-ARIMA-to-identify-optimal-lag/m-p/680582#M3949</guid>
      <dc:creator>Golf</dc:creator>
      <dc:date>2020-09-01T00:21:17Z</dc:date>
    </item>
    <item>
      <title>Re: proc ARIMA to identify optimal lag</title>
      <link>https://communities.sas.com/t5/SAS-Forecasting-and-Econometrics/proc-ARIMA-to-identify-optimal-lag/m-p/680747#M3950</link>
      <description>&lt;P&gt;You are most welcome,&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/313878"&gt;@Golf&lt;/a&gt;.&amp;nbsp; Happy to help!&lt;/P&gt;</description>
      <pubDate>Tue, 01 Sep 2020 16:31:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Forecasting-and-Econometrics/proc-ARIMA-to-identify-optimal-lag/m-p/680747#M3950</guid>
      <dc:creator>dw_sas</dc:creator>
      <dc:date>2020-09-01T16:31:38Z</dc:date>
    </item>
  </channel>
</rss>

