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
Is your feature request related to a problem? Please describe.
I have some time series data at weekly granularity, but some weeks have NaN or None values.
The pmdarima auto_arima documentation says that the input time series data should not contain any np.nan or np.inf values. So I cannot use auto_arima without imputing values. This is unlike pmdarima arima, which allows the use of input data with NaN or None values. The same is true of the R auto.arima package.
Describe the solution you'd like
auto_arima should work with missing values. For example, [1, 3, 4, None, 5, 2, 3, None, 7] should not raise ValueError: Input y contains NaN, and auto_arima should train as normal.
Describe alternatives you've considered
Imputing values, but this means the model trains on incorrect data, and reproduces this 'synthetic data' pattern in future predictions.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I have some time series data at weekly granularity, but some weeks have NaN or None values.
The pmdarima auto_arima documentation says that the input time series data should not contain any np.nan or np.inf values. So I cannot use auto_arima without imputing values. This is unlike pmdarima arima, which allows the use of input data with NaN or None values. The same is true of the R auto.arima package.
Describe the solution you'd like
auto_arima should work with missing values. For example, [1, 3, 4, None, 5, 2, 3, None, 7] should not raise ValueError: Input y contains NaN, and auto_arima should train as normal.
Describe alternatives you've considered
Imputing values, but this means the model trains on incorrect data, and reproduces this 'synthetic data' pattern in future predictions.
Additional Context
No response
The text was updated successfully, but these errors were encountered: