Open elray1 opened 4 years ago
Seems like there are two issues.
I don't think there's much to do about either of these things.
The best option I can see would be to modify forecast::auto.arima to optionally return a list of any fully-fit models with parameter estimates, and accept such a list to use as initial values for parameters being estimated via MLE in the if(method == "CSS-ML") block in stats::arima. Then we could save the results from previous weeks or years fits and use them to get better(?) initial values for the current estimation task.
setting max.p and max.q to 4 instead of 5 did not help
Estimation process taking a long time for many fits recently. Seems to have to do with a call to optim under the if (method == "CSS-ML") { block in stats::arima, called from the if (approximation && !is.null(bestfit$arma)) { block in forecast::auto.arima.
Can we provide another option for method, a maxit for optim calls, or figure out what the underlying problem is? maybe we need to have lower limits on maxp and maxq for auto.arima?