PyDLM 
Welcome to pydlm, a flexible time series modeling library for python. This library is based on the Bayesian dynamic linear model (Harrison and West, 1999) and optimized for fast model fitting and inference.
Updates in the github version
- A temporary fix on the
predict()complexity bug (due to incorrect self-referencing, thanks romainjln@ and buhbuhtig@!). The fixedpredict()complxity is O(n). The goal is to make it O(1). - A lite version pydlm-lite has been created where dependencies on
matplotlibwas removed. Going forward, most code refactoring on improving multi-threading and online learning will be done on thepydlm-litepackage. The development onpydlmpackage will primarily focus on supporting broader model classes and more advanced sampling algorithms. - Version 0.1.1.11 released on PyPI.
Installation
You can get the package (current version 0.1.1.11) from pypi by
$ pip install pydlm
You can also get the latest from github
$ git clone [email protected]:wwrechard/pydlm.git pydlm
$ cd pydlm
$ sudo python setup.py install
pydlm depends on the following modules,
numpy(for core functionality)matplotlib(for plotting results)Sphinx(for generating documentation)unittest(for testing)
Google data science post example
We use the example from the Google data science post as an example to show how pydlm could be used to analyze the real world data. The code and data is placed under examples/unemployment_insurance/.... The dataset contains weekly counts of initial claims for unemployment during 2004 - 2012 and is available from the R package bsts (which is a popular R package for time series modeling). The raw data is shown below (left)
A simple model
Following the Google's post, we first build a simple model with only local linear trend and seasonality component.from pydlm import dlm, trend, seasonality
# A linear trend
linear_trend = trend(degree=1, discount=0.95, name='linear_trend', w=10)
# A seasonality
seasonal52 = seasonality(period=52, discount=0.99, name='seasonal52', w=10)
# Build a simple dlm
simple_dlm = dlm(time_series) + linear_trend + seasonal52
In the actual code, the time series data is scored in the variable time_series. degree=1 indicates the trend is linear (2 stands for quadratic) and period=52 means the seasonality has a periodicy of 52. Since the seasonality is generally more stable, we set its discount factor to 0.99. For local linear trend, we use 0.95 to allow for some flexibility. w=10 is the prior guess on the variance of each component, the larger number the more uncertain. For actual meaning of these parameters, please refer to the user manual. After the model built, we can fit the model and plot the result (shown above, right figure)
# Fit the model
simple_dlm.fit()
# Plot the fitted results
simple_dlm.turnOff('data points')
simple_dlm.plot()
The blue curve is the forward filtering result, the green curve is the one-day ahead prediction and the red curve is the backward smoothed result. The light-colored ribbon around the curve is the confidence interval (you might need to zoom-in to see it). The one-day ahead prediction shows this simple model captures the time series somewhat good but loses accuracy around the peak crisis at Week 280 (which is between year 2008 - 2009). The one-day-ahead mean squared prediction error is 0.173 which can be obtained by calling
simple_dlm.getMSE()
We can decompose the time series into each of its components
# Plot each component (attribute the time series to each component)
simple_dlm.turnOff('predict plot')
simple_dlm.turnOff('filtered plot')
simple_dlm.plot('linear_trend')
simple_dlm.plot('seasonal52')
Most of the time series shape is attributed to the local linear trend and the strong seasonality pattern is easily seen. To further verify the performance, we use this simple model for long-term forecasting. In particular, we use the previous 351 week's data to forecast the next 200 weeks and the previous 251 week's data to forecast the next 200 weeks. We lay the predicted results on top of the real data
# Plot the prediction give the first 351 weeks and forcast the next 200 weeks.
simple_dlm.plotPredictN(date=350, N=200)
# Plot the prediction give the first 251 weeks and forcast the next 200 weeks.
simple_dlm.plotPredictN(date=250, N=200)
From the figure we see that after the crisis peak around 2008 - 2009 (Week 280), the simple model can accurately forecast the next 200 weeks (left figure) given the first 351 weeks. However, the model fails to capture the change near the peak if the forecasting start before Week 280 (right figure).
Dynamic linear regression
Now we build a more sophiscated model with extra variables in the data file. The extra variables are stored in the variable `features` in the actual code. To build the dynamic linear regression model, we simply add a new component# Build a dynamic regression model
from pydlm import dynamic
regressor10 = dynamic(features=features, discount=1.0, name='regressor10', w=10)
drm = dlm(time_series) + linear_trend + seasonal52 + regressor10
drm.fit()
drm.getMSE()
# Plot the fitted results
drm.turnOff('data points')
drm.plot()
dynamic is the component for modeling dynamically changing predictors, which accepts features as its argument. The above code plots the fitted result (top left).
The one-day ahead prediction looks much better than the simple model, particularly around the crisis peak. The mean prediction error is 0.099 which is a 100% improvement over the simple model. Similarly, we also decompose the time series into the three components
drm.turnOff('predict plot')
drm.turnOff('filtered plot')
drm.plot('linear_trend')
drm.plot('seasonal52')
drm.plot('regressor10')
This time, the shape of the time series is mostly attributed to the regressor and the linear trend looks more linear. If we do long-term forecasting again, i.e., use the previous 301 week's data to forecast the next 150 weeks and the previous 251 week's data to forecast the next 200 weeks
drm.plotPredictN(date=300, N=150)
drm.plotPredictN(date=250, N=200)
The results look much better compared to the simple model
Documentation
Detailed documentation is provided in PyDLM with special attention to the User manual.
How should I proceed with the same? You documentations lacks some notations, adding which would be really beneficial. But nice work. Its really useful in my research
3.3k Jan 3, 2023
2k Jan 2, 2023
1.3k Dec 22, 2022
5.2k Jan 4, 2023
2.5k Jan 6, 2023
216 Dec 30, 2022
401 Jan 8, 2023
1.4k Jan 1, 2023
536 Dec 29, 2022
888 Dec 30, 2022
465 Jan 2, 2023
3 Nov 24, 2021
179 Dec 31, 2022
2.3k Jan 5, 2023
15.4k Jan 7, 2023
7k Jan 6, 2023
6k Jan 6, 2023
2.5k Jan 2, 2023