You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: fun_with_astsa/fun_with_astsa.md
+14-3Lines changed: 14 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -713,10 +713,12 @@ It can do everything for you but you have to choose the model ... speaking of wh
713
713
714
714
715
715
716
+
---
717
+
716
718
❌ Don't use black boxes like `auto.arima` from the `forecast` package because IT DOESN'T WORK well. If you know what you are doing, fitting an ARIMA model to linear time series data is easy.
🤣🤣🤣 ... an ARMA(2,1) ?? BUT, if you KNOW what you are doing, you realize the model is basically overparametrized white noise ... CHECK IT OUT:
748
+
749
+
```r
750
+
arma.check(ar=c(-.9744, -.0477), ma=.9509)
751
+
752
+
WARNING: (Possible) ParameterRedundancy
753
+
754
+
ItlookslikethatARMAmodel has (approximate) commonfactors.
755
+
Thismeansthatthemodel is (possibly) over-parameterized.
756
+
Youmightwanttotryagain.
757
+
```
746
758
747
759
Here's another humorous example. Using the data `cmort` (cardiovascular mortality)
Yep!! 1 parameter with a decent standard error and the residuals are perfect (white and normal).
780
792
781
793
---
782
-
</blockquote>
783
794
784
795
👽 Ok - back to our regularly scheduled program, `sarima()`. As with everything else, there are many examples on the help page (`?sarima`) and we'll do a couple here.
0 commit comments