How to Create an ARIMA Model for Time Series Forecasting with Python

A popular and widely used statistical method for time series forecasting is the ARIMA model.

ARIMA is an acronym that stands for AutoRegressive Integrated Moving Average. It is a class of model that captures a suite of different standard temporal structures in time series data.

In this tutorial, you will discover how to develop an ARIMA model for time series data with Python.

After completing this tutorial, you will know:

  • About the ARIMA model the parameters used and assumptions made by the model.
  • How to fit an ARIMA model to data and use it to make forecasts.
  • How to configure the ARIMA model on your time series problem.

Let’s get started.

Autoregressive Integrated Moving Average Model

An ARIMA model is a class of statistical models for analyzing and forecasting time series data.

It explicitly caters to a suite of standard structures in time series data, and as such provides a simple yet powerful method for making skillful time series forecasts.

ARIMA is an acronym that stands for AutoRegressive Integrated Moving Average. It is a generalization of the simpler AutoRegressive Moving Average and adds the notion of integration.

This acronym is descriptive, capturing the key aspects of the model itself. Briefly, they are:

  • AR: Autoregression. A model that uses the dependent relationship between an observation and some number of lagged observations.
  • I: Integrated. The use of differencing of raw observations (e.g. subtracting an observation from an observation at the previous time step) in order to make the time series stationary.
  • MA: Moving Average. A model that uses the dependency between an observation and a residual error from a moving average model applied to lagged observations.

Each of these components are explicitly specified in the model as a parameter. A standard notation is used of ARIMA(p,d,q) where the parameters are substituted with integer values to quickly indicate the specific ARIMA model being used.

The parameters of the ARIMA model are defined as follows:

  • p: The number of lag observations included in the model, also called the lag order.
  • d: The number of times that the raw observations are differenced, also called the degree of differencing.
  • q: The size of the moving average window, also called the order of moving average.

A linear regression model is constructed including the specified number and type of terms, and the data is prepared by a degree of differencing in order to make it stationary, i.e. to remove trend and seasonal structures that negatively affect the regression model.

A value of 0 can be used for a parameter, which indicates to not use that element of the model. This way, the ARIMA model can be configured to perform the function of an ARMA model, and even a simple AR, I, or MA model.

Adopting an ARIMA model for a time series assumes that the underlying process that generated the observations is an ARIMA process. This may seem obvious, but helps to motivate the need to confirm the assumptions of the model in the raw observations and in the residual errors of forecasts from the model.

Next, let’s take a look at how we can use the ARIMA model in Python. We will start with loading a simple univariate time series.

Stop learning Time Series Forecasting the slow way

Sign-up and get a FREE 7-day Time Series Forecasting Mini-Course

You will get: lesson each day delivered to your inbox
...exclusive PDF ebook containing all lessons
...confidence and skills to work through your own projects

Download Your FREE Mini-Course

Shampoo Sales Dataset

This dataset describes the monthly number of sales of shampoo over a 3 year period.

The units are a sales count and there are 36 observations. The original dataset is credited to Makridakis, Wheelwright, and Hyndman (1998).

Learn more about the dataset and download it from here.

Download the dataset and place it in your current working directory with the filename “shampoo-sales.csv“.

Below is an example of loading the Shampoo Sales dataset with Pandas with a custom function to parse the date-time field. The dataset is baselined in an arbitrary year, in this case 1900.

Running the example prints the first 5 rows of the dataset.

The data is also plotted as a time series with the month along the x-axis and sales figures on the y-axis.

Shampoo Sales Dataset Plot

Shampoo Sales Dataset Plot

We can see that the Shampoo Sales dataset has a clear trend.

This suggests that the time series is not stationary and will require differencing to make it stationary, at least a difference order of 1.

Let’s also take a quick look at an autocorrelation plot of the time series. This is also built-in to Pandas. The example below plots the autocorrelation for a large number of lags in the time series.

Running the example, we can see that there is a positive correlation with the first 10-to-12 lags that is perhaps significant for the first 5 lags.

A good starting point for the AR parameter of the model may be 5.

Autocorrelation Plot of Shampoo Sales Data

Autocorrelation Plot of Shampoo Sales Data

ARIMA with Python

The statsmodels library provides the capability to fit an ARIMA model.

An ARIMA model can be created using the statsmodels library as follows:

  1. Define the model by calling ARIMA() and passing in the p, d, and q parameters.
  2. The model is prepared on the training data by calling the fit() function.
  3. Predictions can be made by calling the predict() function and specifying the index of the time or times to be predicted.

Let’s start off with something simple. We will fit an ARIMA model to the entire Shampoo Sales dataset and review the residual errors.

First, we fit an ARIMA(5,1,0) model. This sets the lag value to 5 for autoregression, uses a difference order of 1 to make the time series stationary, and uses a moving average model of 0.

When fitting the model, a lot of debug information is provided about the fit of the linear regression model. We can turn this off by setting the disp argument to 0.

Running the example prints a summary of the fit model. This summarizes the coefficient values used as well as the skill of the fit on the on the in-sample observations.

First, we get a line plot of the residual errors, suggesting that there may still be some trend information not captured by the model.

ARMA Fit Residual Error Line Plot

ARMA Fit Residual Error Line Plot

Next, we get a density plot of the residual error values, suggesting the errors are Gaussian, but may not be centered on zero.

ARMA Fit Residual Error Density Plot

ARMA Fit Residual Error Density Plot

The distribution of the residual errors is displayed. The results show that indeed there is a bias in the prediction (a non-zero mean in the residuals).

Note, that although above we used the entire dataset for time series analysis, ideally we would perform this analysis on just the training dataset when developing a predictive model.

Next, let’s look at how we can use the ARIMA model to make forecasts.

Rolling Forecast ARIMA Model

The ARIMA model can be used to forecast future time steps.

We can use the predict() function on the ARIMAResults object to make predictions. It accepts the index of the time steps to make predictions as arguments. These indexes are relative to the start of the training dataset used to make predictions.

If we used 100 observations in the training dataset to fit the model, then the index of the next time step for making a prediction would be specified to the prediction function as start=101, end=101. This would return an array with one element containing the prediction.

We also would prefer the forecasted values to be in the original scale, in case we performed any differencing (d>0 when configuring the model). This can be specified by setting the typ argument to the value ‘levels’: typ=’levels’.

Alternately, we can avoid all of these specifications by using the forecast() function, which performs a one-step forecast using the model.

We can split the training dataset into train and test sets, use the train set to fit the model, and generate a prediction for each element on the test set.

A rolling forecast is required given the dependence on observations in prior time steps for differencing and the AR model. A crude way to perform this rolling forecast is to re-create the ARIMA model after each new observation is received.

We manually keep track of all observations in a list called history that is seeded with the training data and to which new observations are appended each iteration.

Putting this all together, below is an example of a rolling forecast with the ARIMA model in Python.

Running the example prints the prediction and expected value each iteration.

We can also calculate a final mean squared error score (MSE) for the predictions, providing a point of comparison for other ARIMA configurations.

A line plot is created showing the expected values (blue) compared to the rolling forecast predictions (red). We can see the values show some trend and are in the correct scale.

ARIMA Rolling Forecast Line Plot

ARIMA Rolling Forecast Line Plot

The model could use further tuning of the p, d, and maybe even the q parameters.

Configuring an ARIMA Model

The classical approach for fitting an ARIMA model is to follow the Box-Jenkins Methodology.

This is a process that uses time series analysis and diagnostics to discover good parameters for the ARIMA model.

In summary, the steps of this process are as follows:

  1. Model Identification. Use plots and summary statistics to identify trends, seasonality, and autoregression elements to get an idea of the amount of differencing and the size of the lag that will be required.
  2. Parameter Estimation. Use a fitting procedure to find the coefficients of the regression model.
  3. Model Checking. Use plots and statistical tests of the residual errors to determine the amount and type of temporal structure not captured by the model.

The process is repeated until either a desirable level of fit is achieved on the in-sample or out-of-sample observations (e.g. training or test datasets).

The process was described in the classic 1970 textbook on the topic titled Time Series Analysis: Forecasting and Control by George Box and Gwilym Jenkins. An updated 5th edition is now available if you are interested in going deeper into this type of model and methodology.

Given that the model can be fit efficiently on modest-sized time series datasets, grid searching parameters of the model can be a valuable approach.


In this tutorial, you discovered how to develop an ARIMA model for time series forecasting in Python.

Specifically, you learned:

  • About the ARIMA model, how it can be configured, and assumptions made by the model.
  • How to perform a quick time series analysis using the ARIMA model.
  • How to use an ARIMA model to forecast out of sample predictions.

Do you have any questions about ARIMA, or about this tutorial?
Ask your questions in the comments below and I will do my best to answer.

Want to Develop Time Series Forecasts with Python?

Introduction to Time Series Forecasting With Python

Develop Your Own Forecasts in Minutes

...with just a few lines of python code

Discover how in my new Ebook:
Introduction to Time Series Forecasting With Python

It covers self-study tutorials and end-to-end projects on topics like:
Loading data, visualization, modeling, algorithm tuning, and much more...

Finally Bring Time Series Forecasting to
Your Own Projects

Skip the Academics. Just Results.

Click to learn more.

62 Responses to How to Create an ARIMA Model for Time Series Forecasting with Python

  1. SalemAmeen January 9, 2017 at 7:22 am #

    Many thank

  2. Blessing Ojeme January 9, 2017 at 1:20 pm #

    Much appreciated, Jason. Keep them coming, please.

    • Jason Brownlee January 10, 2017 at 8:55 am #

      Sure thing! I’m glad you’re finding them useful.

      What else would you like to see?

  3. Chow Xixi January 9, 2017 at 6:00 pm #

    good,Has been paid close attention to your blog.

  4. Kevin January 17, 2017 at 12:58 am #

    Gives me loads of errors:

    Traceback (most recent call last):
    File “/Users/kevinoost/anaconda/lib/python3.5/site-packages/pandas/io/”, line 2276, in converter
    date_parser(*date_cols), errors=’ignore’)
    File “/Users/kevinoost/PycharmProjects/ARIMA/”, line 6, in parser
    return datetime.strptime(‘190’+x, ‘%Y-%m’)
    TypeError: strptime() argument 1 must be str, not numpy.ndarray

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
    File “/Users/kevinoost/anaconda/lib/python3.5/site-packages/pandas/io/”, line 2285, in converter
    File “pandas/src/inference.pyx”, line 841, in pandas.lib.try_parse_dates (pandas/lib.c:57884)
    File “pandas/src/inference.pyx”, line 838, in pandas.lib.try_parse_dates (pandas/lib.c:57802)
    File “/Users/kevinoost/PycharmProjects/ARIMA/”, line 6, in parser
    return datetime.strptime(‘190’+x, ‘%Y-%m’)
    File “/Users/kevinoost/anaconda/lib/python3.5/”, line 510, in _strptime_datetime
    tt, fraction = _strptime(data_string, format)
    File “/Users/kevinoost/anaconda/lib/python3.5/”, line 343, in _strptime
    (data_string, format))
    ValueError: time data ‘190Sales of shampoo over a three year period’ does not match format ‘%Y-%m’

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
    File “/Users/kevinoost/PycharmProjects/ARIMA/”, line 8, in
    series = read_csv(‘shampoo-sales.csv’, header=0, parse_dates=[0], index_col=0, squeeze=True, date_parser=parser)
    File “/Users/kevinoost/anaconda/lib/python3.5/site-packages/pandas/io/”, line 562, in parser_f
    return _read(filepath_or_buffer, kwds)
    File “/Users/kevinoost/anaconda/lib/python3.5/site-packages/pandas/io/”, line 325, in _read
    File “/Users/kevinoost/anaconda/lib/python3.5/site-packages/pandas/io/”, line 815, in read
    ret =
    File “/Users/kevinoost/anaconda/lib/python3.5/site-packages/pandas/io/”, line 1387, in read
    index, names = self._make_index(data, alldata, names)
    File “/Users/kevinoost/anaconda/lib/python3.5/site-packages/pandas/io/”, line 1030, in _make_index
    index = self._agg_index(index)
    File “/Users/kevinoost/anaconda/lib/python3.5/site-packages/pandas/io/”, line 1111, in _agg_index
    arr = self._date_conv(arr)
    File “/Users/kevinoost/anaconda/lib/python3.5/site-packages/pandas/io/”, line 2288, in converter
    return generic_parser(date_parser, *date_cols)
    File “/Users/kevinoost/anaconda/lib/python3.5/site-packages/pandas/io/”, line 38, in generic_parser
    results[i] = parse_func(*args)
    File “/Users/kevinoost/PycharmProjects/ARIMA/”, line 6, in parser
    return datetime.strptime(‘190’+x, ‘%Y-%m’)
    File “/Users/kevinoost/anaconda/lib/python3.5/”, line 510, in _strptime_datetime
    tt, fraction = _strptime(data_string, format)
    File “/Users/kevinoost/anaconda/lib/python3.5/”, line 343, in _strptime
    (data_string, format))
    ValueError: time data ‘190Sales of shampoo over a three year period’ does not match format ‘%Y-%m’

    Process finished with exit code 1

    Help would be much appreciated.

    • Jason Brownlee January 17, 2017 at 7:39 am #

      It looks like there might be an issue with your data file.

      Open the csv in a text editor and confirm the header line looks sensible.

      Also confirm that you have no extra data at the end of the file. Sometimes the datamarket files download with footer data that you need to delete.

  5. NGUYEN Quang Anh January 19, 2017 at 6:28 pm #

    Let say I have a time series data with many attribute. For example a row will have (speed, fuel, tire_pressure), how could we made a model out of this ? the value of each column may affect each other, so we cannot do forecasting on solely 1 column. I google a lot but all the example I’ve found so far only work on time series of 1 attribute.

  6. Kelvid January 20, 2017 at 11:55 am #

    Hi, would you have a example for the seasonal ARIMA post? I have installed latest statsmodels module, but there is an error of import the SARIMAX. Do help if you manage to figure it out. Thanks.

    • Jason Brownlee January 21, 2017 at 10:23 am #

      Hi Kelvid, I don’t have one at the moment. I ‘ll prepare an example of SARIMAX and post it soon.

  7. Muhammad Arsalan January 29, 2017 at 10:13 pm #

    It is so informative..thankyou

  8. Sebastian January 31, 2017 at 3:33 am #

    Great post Jason!

    I have a couple of questions:

    – Just to be sure. model_fit.forecast() is single step ahead forecasts and model_fit.predict() is for multiple step ahead forecasts?

    – I am working with a series that seems at least quite similar to the shampoo series (by inspection). When I use predict on the training data, I get this zig-zag pattern in the prediction as well. But for the test data, the prediction is much smoother and seems to saturate at some level. Would you expect this? If not, what could be wrong?

    • Jason Brownlee February 1, 2017 at 10:28 am #

      Hi Sebastian,

      Yes, forecast() is for one step forecasts. You can do one step forecasts with predict() also, but it is more work.

      I would not expect prediction beyond a few time steps to be very accurate, if that is your question?

      • Sebastian February 3, 2017 at 9:25 am #

        Thanks for the reply!

        Concerning the second question. Yes, you are right the prediction is not very accurate. But moreover, the predicted time series has a totally different frequency content. As I said, it is smooth and not zig-zaggy as the original data. Is this normal or am I doing something wrong. I also tried the multiple step prediction (model_fit.predict()) on the training data and then the forecast seem to have more or less the same frequency content (more zig-zaggy) as the data I am trying to predict.

        • Jason Brownlee February 3, 2017 at 10:22 am #

          Hi Sebastian, I see.

          In the case of predicting on the training dataset, the model has access to real observations. For example, if you predict the next 5 obs somewhere in the training dataset, it will use obs(t+4) to predict t+5 rather than prediction(t+4).

          In the case of predicting beyond the end of the model data, it does not have obs to make predictions (unless you provide them), it only has access to the predictions it made for prior time steps. The result is the errors compound and things go off the rails fast (flat forecast).

          Does that make sense/help?

          • Sebastian February 3, 2017 at 6:34 pm #

            That helped!


          • Jason Brownlee February 4, 2017 at 10:00 am #

            Glad to hear it Sebastian.

  9. Elliot January 31, 2017 at 10:07 am #

    So this is building a model and then checking it off of the given data right?

    -How can I predict what would come next after the last data point? Am I misunderstanding the code?

  10. Muyi Ibidun February 7, 2017 at 9:38 am #

    Thanks Jason for this post!

    It was really useful. And your blogs are becoming a must read for me because of the applicable and piecemeal nature of your tutorials.

    Keep up the good work!

  11. Kalin Stoyanov February 8, 2017 at 9:30 pm #

    This is not the first post on ARIMA, but it is the best so far. Thank you.

  12. James Zhang February 10, 2017 at 7:42 pm #

    Hey Jason,

    thank you very much for the post, very good written! I have a question: so I used your approach to build the model, but when I try to forecast the data that are out of sample, I commented out the obs = test[t] and change history.append(obs) to history.append(yhat), and I got a flat prediction… so what could be the reason? and how do you actually do the out-of-sample predictions based on the model fitted on train dataset? Thank you very much!

    • Jason Brownlee February 11, 2017 at 5:00 am #

      Hi james,

      Each loop in the rolling forecast shows you how to make a one-step out of sample forecast.

      Train your ARIMA on all available data and call forecast().

      If you want to perform a multi-step forecast, indeed, you will need to treat prior forecasts as “observations” and use them for subsequent forecasts. You can do this automatically using the predict() function. Depending on the problem, this approach is often not skillful (e.g. a flat forecast).

      Does that help?

      • James February 16, 2017 at 2:03 am #

        Hi Jason,

        thank you for you reply! so what could be the reason a flat forecast occurs and how to avoid it?

        • Jason Brownlee February 16, 2017 at 11:09 am #

          Hi James,

          The model may not have enough information to make a good forecast.

          Consider exploring alternate methods that can perform multi-step forecasts in one step – like neural nets or recurrent neural nets.

          • James February 16, 2017 at 7:41 pm #

            Hi Jason,

            thanks a lot for your information! still need to learn a lot from people like you! 😀 nice day!

          • Jason Brownlee February 17, 2017 at 9:53 am #

            I’m here to help James!

  13. Supriya February 16, 2017 at 1:27 am #

    when i calculate train and test error , train rmse is greater than test rmse.. why is it so?

    • Jason Brownlee February 16, 2017 at 11:08 am #

      I see this happen sometimes Supriya.

      It suggests the model may not be well suited for the data.

  14. Matias T February 18, 2017 at 12:04 am #

    Hello Jason, thanks for this amazing post.
    I was wondering how does the “size” work here. For example lets say i want to forecast only 30 days ahead. I keep getting problems with the degrees of freedom.
    Could you please explain this to me.


    • Jason Brownlee February 18, 2017 at 8:40 am #

      Hi Matias, the “size” in the example is used to split the data into train/test sets for model evaluation using walk forward validation.

      You can set this any way you like or evaluate your model different ways.

      To forecast 30 days ahead, you are going to need a robust model and enough historic data to evaluate this model effectively.

      • Matias R February 21, 2017 at 6:39 am #

        I get it. Thanks Jason.

        I was thinking, in this particular example, ¿will the prediction change if we keep adding data?

        • Jason Brownlee February 21, 2017 at 9:41 am #

          Great question Matias.

          The amount of history is one variable to test with your model.

          Design experiments to test if having more or less history improves performance.

  15. ubald kuijpers February 24, 2017 at 10:05 pm #

    Dear Jason,

    Thank you for explaining the ARIMA model in such clear detail.
    It helped me to make my own model to get numerical forrcasts and store it in a database.
    So nice that we live in an era where knowledge is de-mystified .

  16. Jacques Sauve February 25, 2017 at 6:41 am #

    Hi Jason. Very good work!
    It would be great to see how forecasting models can be used to detect anomalies in time series. thanks.

  17. Mehran March 1, 2017 at 12:56 am #

    Hi there. Many thanks. I think you need to change the way you parse the datetime to:

    datetime.strptime(’19’+x, ‘%Y-%b’)

    Many thanks

    • Jason Brownlee March 1, 2017 at 8:41 am #

      Are you sure?

      See this list of abbreviations:

      The “%m” refers to “Month as a zero-padded decimal number.” which is exactly what we have here.

      See a sample of the raw data file:

      The “%b” refers to “Month as locale’s abbreviated name.” which we do not have here.

  18. Niirkshith March 6, 2017 at 4:49 pm #

    Hi Jason,
    Lucky i found this at the begining of my project.. Its a great start point and enriching.
    Keep it coming :).
    This can also be used for non linear time series as well?


  19. Anthony of Sydney March 8, 2017 at 9:00 am #

    Dear Dr Jason,

    In the above example of the rolling forecast, you used the rmse of the predicted and the actual value.

    Another way of getting the residuals of the model is to get the std devs of the residuals of the fitted model

    Question, is the std dev of the residuals the same as the root_mean_squared(actual, predicted)?
    Thank you
    Anthony of Sydney NSW

    what is the difference between measuring the std deviation of the residuals of a fitted model and the rmse of the rolling forecast will

  20. Niirkshith March 10, 2017 at 1:28 pm #

    Hi Jason,
    Great writeup, had a query, when u have a seasonal data and do seasonal differencing. i.e for exy(t)=y(t)-y(t-12) for yearly data. What will be the value of d in ARIMA(p,d,q).

    • Niirkshith March 10, 2017 at 1:29 pm #

      typo, ex y(t)=y(t)-y(t-12) for monthly data not yearly

    • Jason Brownlee March 11, 2017 at 7:56 am #

      Great question Niirkshith.

      ARIMA will not do seasonal differencing (there is a version that will called SARIMA). The d value on ARIMA will be unrelated to the seasonal differencing and will assume the input data is already seasonally adjusted.

  21. Niirkshith March 13, 2017 at 1:09 pm #

    Thanks for getting back.

  22. ivan March 19, 2017 at 5:17 am #

    Hi, Jason

    thanks for this example. My question how is chosen the parameter q ?
    best Ivan

  23. Narbukra March 30, 2017 at 4:21 am #

    Hi Jason, I am wondering if you did a similar tutorial on multi-variate time series forecasting?

  24. David March 30, 2017 at 8:53 am #

    Hi Jason,

    Thanks for the great post! It was very helpful. I’m currently trying to forecast with the ARIMA model using order (4, 1, 5) and I’m getting an error message “The computed initial MA coefficients are not invertible. You should induce invertibility, choose a different model order, or you can pass your own start_params.” The model works when fitting, but seems to error out when I move to model_fit = The forecast works well when using your parameters of (0, 1, 5) and I used ACF and PACF plots to find my initial p and q parameters. Any ideas on the cause/fix for the error? Any tips would be much appreciated.

  25. tom reilly April 27, 2017 at 6:39 am #

    It’s a great blog that you have, but the PACF determines the AR order not the ACF.

Leave a Reply