How to Make Predictions for Time Series Forecasting with Python

Selecting a time series forecasting model is just the beginning.

Using the chosen model in practice can pose challenges, including data transformations and storing the model parameters on disk.

In this tutorial, you will discover how to finalize a time series forecasting model and use it to make predictions in Python.

After completing this tutorial, you will know:

  • How to finalize a model and save it and required data to file.
  • How to load a finalized model from file and use it to make a prediction.
  • How to update data associated with a finalized model in order to make subsequent predictions.

Let’s get started.

  • Update Feb/2017: Updated layout and filenames to separate the AR case from the manual case.
How to Make Predictions for Time Series Forecasting with Python

How to Make Predictions for Time Series Forecasting with Python
Photo by joe christiansen, some rights reserved.

Process for Making a Prediction

A lot is written about how to tune specific time series forecasting models, but little help is given to how to use a model to make predictions.

Once you can build and tune forecast models for your data, the process of making a prediction involves the following steps:

  1. Model Selection. This is where you choose a model and gather evidence and support to defend the decision.
  2. Model Finalization. The chosen model is trained on all available data and saved to file for later use.
  3. Forecasting. The saved model is loaded and used to make a forecast.
  4. Model Update. Elements of the model are updated in the presence of new observations.

We will take a look at each of these elements in this tutorial, with a focus on saving and loading the model to and from file and using a loaded model to make predictions.

Before we dive in, let’s first look at a standard univariate dataset that we can use as the context for this tutorial.

Stop learning Time Series Forecasting the slow way!

Take my free 7-day email course and discover how to get started (with sample code).

Click to sign-up and also get a free PDF Ebook version of the course.

Start Your FREE Mini-Course Now!

Daily Female Births Dataset

This dataset describes the number of daily female births in California in 1959.

The units are a count and there are 365 observations. The source of the dataset is credited to Newton (1988).

Learn more and download the dataset from Data Market.

Download the dataset and place it in your current working directory with the filename “daily-total-female-births.csv“.

We can load the dataset as a Pandas series. The snippet below loads and plots the dataset.

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

The series is then graphed as a line plot.

Daily Female Birth Dataset Line Plot

Daily Female Birth Dataset Line Plot

1. Select Time Series Forecast Model

You must select a model.

This is where the bulk of the effort will be in preparing the data, performing analysis, and ultimately selecting a model and model hyperparameters that best capture the relationships in the data.

In this case, we can arbitrarily select an autoregression model (AR) with a lag of 6 on the differenced dataset.

We can demonstrate this model below.

First, the data is transformed by differencing, with each observation transformed as:

Next, the AR(6) model is trained on 66% of the historical data. The regression coefficients learned by the model are extracted and used to make predictions in a rolling manner across the test dataset.

As each time step in the test dataset is executed, the prediction is made using the coefficients and stored. The actual observation for the time step is then made available and stored to be used as a lag variable for future predictions.

Running the example first prints the Mean Squared Error (MSE) of the predictions, which is 52 (or about 7 births on average, if we take the square root to return the error score to the original units).

This is how well we expect the model to perform on average when making forecasts on new data.

Finally, a graph is created showing the actual observations in the test dataset (blue) compared to the predictions (red).

Predictions vs Actual Daily Female Birth Dataset Line Plot

Predictions vs Actual Daily Female Birth Dataset Line Plot

This may not be the very best possible model we could develop on this problem, but it is reasonable and skillful.

2. Finalize and Save Time Series Forecast Model

Once the model is selected, we must finalize it.

This means save the salient information learned by the model so that we do not have to re-create it every time a prediction is needed.

This involves first training the model on all available data and then saving the model to file.

The statsmodels implementations of time series models do provide built-in capability to save and load models by calling save() and load() on the fit ARResults object.

For example, the code below will train an AR(6) model on the entire Female Births dataset and save it using the built-in save() function, which will essentially pickle the ARResults object.

The differenced training data must also be saved, both the for the lag variables needed to make a prediction, and for knowledge of the number of observations seen, required by the predict() function of the ARResults object.

Finally, we need to be able to transform the differenced dataset back into the original form. To do this, we must keep track of the last actual observation. This is so that the predicted differenced value can be added to it.

This code will create a file ar_model.pkl that you can load later and use to make predictions.

The entire training dataset is saved as ar_data.npy and the last observation is saved in the file ar_obs.npy as an array with one item.

The NumPy save() function is used to save the differenced training data and the observation. The load() function can then be used to load these arrays later.

The snippet below will load the model, differenced data, and last observation.

Running the example prints the coefficients and the last observation.

I think this is good for most cases, but is also pretty heavy. You are subject to changes to the statsmodels API.

My preference is to work with the coefficients of the model directly, as in the case above, evaluating the model using a rolling forecast.

In this case, you could simply store the model coefficients and later load them and make predictions.

The example below saves just the coefficients from the model, as well as the minimum differenced lag values required to make the next prediction and the last observation needed to transform the next prediction made.

The coefficients are saved in the local file man_model.npy, the lag history is saved in the file man_data.npy, and the last observation is saved in the file man_obs.npy.

These values can then be loaded again as follows:

Running this example prints the loaded data for review. We can see the coefficients and last observation match the output from the previous example.

Now that we know how to save a finalized model, we can use it to make forecasts.

3. Make a Time Series Forecast

Making a forecast involves loading the saved model and estimating the observation at the next time step.

If the ARResults object was serialized, we can use the predict() function to predict the next time period.

The example below shows how the next time period can be predicted.

The model, training data, and last observation are loaded from file.

The period is specified to the predict() function as the next time index after the end of the training data set. This index may be stored directly in a file instead of storing the entire training data, which may be an efficiency.

The prediction is made, which is in the context of the differenced dataset. To turn the prediction back into the original units, it must be added to the last known observation.

Running the example prints the prediction.

We can also use a similar trick to load the raw coefficients and make a manual prediction.
The complete example is listed below.

Running the example, we achieve the same prediction as we would expect, given the underlying model and method for making the prediction are the same.

4. Update Forecast Model

Our work is not done.

Once the next real observation is made available, we must update the data associated with the model.

Specifically, we must update:

  1. The differenced training dataset used as inputs to make the subsequent prediction.
  2. The last observation, providing a context for the predicted differenced value.

Let’s assume the next actual observation in the series was 48.
The new observation must first be differenced with the last observation. It can then be stored in the list of differenced observations. Finally, the value can be stored as the last observation.

In the case of the stored AR model, we can update the ar_data.npy and ar_obs.npy files. The complete example is listed below:

We can make the same changes for the data files for the manual case. Specifically, we can update the man_data.npy and man_obs.npy respectively.

The complete example is listed below.

We have focused on one-step forecasts.

These methods would work just as easily for multi-step forecasts, by using the model repetitively and using forecasts of previous time steps as input lag values to predict observations for subsequent time steps.

Consider Storing All Observations

Generally, it is a good idea to keep track of all the observations.

This will allow you to:

  • Provide a context for further time series analysis to understand new changes in the data.
  • Train a new model in the future on the most recent data.
  • Back-test new and different models to see if performance can be improved.

For small applications, perhaps you could store the raw observations in a file alongside your model.

It may also be desirable to store the model coefficients and required lag data and last observation in plain text for easy review.

For larger applications, perhaps a database system could be used to store the observations.

Summary

In this tutorial, you discovered how to finalize a time series model and use it to make predictions with Python.

Specifically, you learned:

  • How to save a time series forecast model to file.
  • How to load a saved time series forecast from file and make a prediction.
  • How to update a time series forecast model with new observations.

Do you have any questions?
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.

22 Responses to How to Make Predictions for Time Series Forecasting with Python

  1. shamsul February 24, 2017 at 7:35 am #

    Great Work sir.

    is it ok to apply time series analysis to predict patients status in ICU using ICU Database such as MIMIC II database? if it is then would be kind enough to guide me on this.

    Thanking you

  2. Hoang March 16, 2017 at 5:50 am #

    Thanks for the tutorial.

    I noticed that when I ran the following code:

    series = pd.read_csv(‘daily-total-female-births.csv’, header=0)

    print(series.head())
    series.plot()
    plt.show()

    I am not getting the same graph. The line graph appears more flat and the months are not showing. Was there additional codes not shown in the tutorial? Also, I tried using pyplot.show() so I update it to plt.show() and the code ran fine.

    Thanks for your help.

    • Jason Brownlee March 16, 2017 at 8:04 am #

      Hi Hoang,

      There’s no additional code.

      Confirm you have the latest version of Pandas and matplotlib installed. Also confirm that your data file contains date-times and observations with no additional data or footer information.

  3. Hoang March 17, 2017 at 4:23 am #

    Thanks Jason, for your quick response.

    I am using Pandas v0.19.2 and matplotlib v2.0.0.

    The additional data was deleted in the data file (thanks to your suggestion) and now the graph looks very similar, however the dates are missing. I’m assuming it’s because the indices are displayed on the x-axis. It was corrected once I set ‘Date’ as the index.

    series=series.set_index(‘Date’)

    The graph doesn’t look exactly like your graph but it’s close enough.

    • Jason Brownlee March 17, 2017 at 8:31 am #

      Glad to hear you made some progress, thanks for providing the details. It may help others.

  4. Nelson Silva July 23, 2017 at 7:59 am #

    Hi Jason, Thank you so much for your nice examples.
    I’ve been wasting my time playing with game results datasets and these first step into prediction was really handy. Usually, in these games there is no tendency at all, all balls have the same fair chance of getting out. How would you approach such predictions, for example for Euromillions?
    Where can I find some more advanced time-series predictions for multivariate cases? I would like to predict the outcome of 3 variables that linked to each other. Similar code to this example would be perfect…

    Thank you

    • Jason Brownlee July 24, 2017 at 6:46 am #

      Do you mean lotto? I believe that is random and not predictable.

      Once you frame your time series as a supervised learning problem, you can use a suite of machine learning methods.

      For predicting 3 variables, I would recommend a neural network model.

  5. Jaskaran August 9, 2017 at 8:36 am #

    Hi Jason,
    Great content as always.

    I had a question.

    1) Why did you not use ARIMA model here and why AR? Is there a difference?

    • Jason Brownlee August 10, 2017 at 6:38 am #

      There is a difference, AR does not include the differencing and moving average. It’s a simpler method.

      It is just an example for making predictions, you could swap in ARIMA if you like.

  6. Martha August 22, 2017 at 3:33 am #

    Hi Jason,

    Really good stuff!

    # make prediction
    predictions = model.predict(start=len(data), end=len(data))

    here the minimum value for start should be window (6 in this case) and less than the end time.

  7. Garrett Dabbs November 19, 2017 at 12:36 pm #

    “These methods would work just as easily for multi-step forecasts, by using the model repetitively and using forecasts of previous time steps as input lag values to predict observations for subsequent time steps.”

    Hello, Jason! I’m a little new to this forecasting modeling approach, and was able to successfully able to run your tutorial and examples no problem. However, as I’m still poking around to see how this works, is there a good example you could point to that explains your above quote? I get that the predict function looks at coef[0] to ultimately perform its calculation, and our forecasting approach provides the next time step’s prediction, but how do I tell the function “look at the NEXT time step after that one…” etc? Is it coef[1]…coef[n]?

    Apologies if these are really dumb questions, I find this fascinating at how accurate it can be on even real world data, and want to do statistical analyses to find out when the “long term forecast” falls off a cliff when it comes to accuracy, I just haven’t been able to figure out how to ask for time steps farther away than 1.

  8. Sash March 27, 2018 at 8:57 am #

    Jason – awesome example.

    Would you use the same method if you say, wanted to predict occupancy on a given floor, of a given building – provided you have time-series data of all of the login’s (and logoffs) of all occupants that come onto the floor – dating back say 1 or 2 years?

    Also, would you use the same method if you wanted to “predict” this occupancy from NOW to say, 2 – 3 days in advance – for a specific day? how would the time-step look like for the next day or in 2 days?

    • Jason Brownlee March 27, 2018 at 4:17 pm #

      Perhaps. Try it and see how it performs on your data.

  9. Sarthak May 12, 2018 at 3:35 am #

    This is a great tutorial. I have a question why did you transform the data?
    And why using difference ?
    Is it necessary to transform the data ?

  10. Amresh August 27, 2018 at 8:26 pm #

    How can I check the prediction performance

    • Jason Brownlee August 28, 2018 at 5:59 am #

      You can calculate the error between predictions and actual values.

  11. Sabrina January 10, 2019 at 1:45 am #

    Hello,
    I will need your advice,
    In fact, I have a large mass of data (almost 200 000), and I want to predict about 1 000 points.
    Which algorithm would be most appropriate?

    My database is univariate (just a data vector)
    If you can direct me to a demo of “online prediction”, with real-time adaptation.

Leave a Reply