Skip navigation links

Package dev.nm.stat.timeseries.linear.univariate.stationaryprocess.arma

ARMA model fitting and forecasting from an ordered observation history.

See: Description

Package dev.nm.stat.timeseries.linear.univariate.stationaryprocess.arma Description

ARMA model fitting and forecasting from an ordered observation history.

Choose a workflow

Prepare data and interpret parameters

Observations must be finite, ordered oldest to newest and sampled on one consistent time grid. Missing periods are a data-modeling decision; dropping rows silently changes the meaning of one lag. These APIs do not resample timestamps, impute missing values or choose the sampling interval.

Coefficient arrays start at lag one, whereas NMDEV observation/vector indices start at one and Java arrays/lists start at zero. A model intercept is not its unconditional mean; for a stationary AR model the mean is \(c/(1-\sum_i\phi_i)\). The sigma constructor argument is innovation variance.

Evaluate a forecast honestly

Choose orders and fit parameters using training observations only. Compare predictions with a chronologically held-out period. Forecast horizon advances on each next call; actual new observations require a new forecaster. Inspect stationarity/invertibility, residual dependence and finite estimates separately from whether the optimizer returned an object.

Consult ARMAForecastMultiStep's current non-unit error-scaling limitation before turning its reported error variances into prediction intervals. The runnable known-model example deliberately uses unit innovation variance.

Skip navigation links

Copyright © 2010-2026 NM Group. All Rights Reserved.