aws / aws/amazon-sagemaker-examples

why do we have to give target time series for nonperiodic time series prediction in DeepAR?

Open
#1,398 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
11k
Forks
7k
Avg merge
8h 29m
Merged PRs (30d)
8

Description

Hi All,

I use DeepAR for time series prediction using multiple input timeseries.
Shortly, I have several timeseries (lets say Input_1, Input_2, Input_3 and Input_5 and TARGET). All these values are from same system and have a relation somehow. In addition, these time-series has no periodic behavior, in other words, there is no seasonality for any of the signals. I want to create a model and predictor for TARGET signal. Figure given below helps to explain behavior. (None of them is periodic)

![0](https://user-images.githubusercontent.com/12895592/90062643-a82cee00-dcf0-11ea-97ca-27fe3adf1974.png)

BLUE signals are input for predictor to forecast RED signal. In other words, I want to generate a model to find how RED behaves when BLUE signals are input.

I choose Sagemaker DeepAR for this problem but there is an issue about DeepAR usage. DeepAR requires context_length parameter to define how far in the past the network can see. Why does DeepAR need this parameter for nonperiodic timeseries? There is no periodic behavior and trend as it can be seen on my plot?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.