Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shifting of Time Series data #1281

Open
Elisa1234567890 opened this issue Feb 19, 2024 · 1 comment
Open

Shifting of Time Series data #1281

Elisa1234567890 opened this issue Feb 19, 2024 · 1 comment

Comments

@Elisa1234567890
Copy link

Hello,

i want to use FLAML to do a time series forecasting task. My dataset is structured as follows: timestamp, demand (output), several different exogenous features (input). One row in the dataset corresponds to the corresponding observations observed at the indicated timestamp. The exogenous features are past covariates that are only known up to the start of the forecast horizon (see Autogluon, past covariates).

As I predict the demand for a timestamp, the exogenous features are only available up to the previous timestamp. Since I am forced to include input variables in the FLAML.predict(), I am wondering whether i need to shift the time series manually beforehand such, that a row constists of the timestamp, the corresponding demand at this timestamp and the exogenous features shifted by the forecast horizon.

@Programmer-RD-AI
Copy link

Programmer-RD-AI commented May 22, 2024

  1. Shifted Model: Exogenous feature are shifted, an advantage is that it provides inputs that directly align with forecast on the other hand it reduces the dataset size.
  2. Unshifted Model: Here, we jus use the exogenous features as they are originally presented, it retains the full dataset but the features may not align with the forecasting which may make it hard to align features with the forecasting data.

The above is the simply aspect of Shifted Model's and Unshifted model's in terms of time series data, so let me know if there are any other questions :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants