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

PatchTST does not yet support historical exogenous variables #847

Closed
wuzeyu6 opened this issue Dec 30, 2023 · 5 comments
Closed

PatchTST does not yet support historical exogenous variables #847

wuzeyu6 opened this issue Dec 30, 2023 · 5 comments
Labels

Comments

@wuzeyu6
Copy link

wuzeyu6 commented Dec 30, 2023

What happened + What you expected to happen

PatchTST does not support covariate-assisted prediction, which I find unfortunate to be a significant reduction in prediction performance

Versions / Dependencies

neuralforecast 1.6.4

Reproduction script

952         if hist_exog_list is not None:

--> 953 raise Exception(
954 "PatchTST does not yet support historical exogenous variables"
955 )

Issue Severity

None

@wuzeyu6 wuzeyu6 added the bug label Dec 30, 2023
@jmoralez jmoralez changed the title Why "PatchTST does not yet support historical exogenous variables[<Library component: Model|Core|etc...>] " PatchTST does not yet support historical exogenous variables Jan 3, 2024
@rd1886
Copy link

rd1886 commented Mar 18, 2024

The same goes for futr_exogenous_list. According to the documentation here, it appears that PatchTST supports futr_exogenous_list. However, when I attempt to run the model with futr_exogenous_list, I encounter the following error:

Exception: PatchTST does not yet support future exogenous variables

@Zhangxixiang77
Copy link

I'm having the same problem, obviously the parameter is there but unfortunately it's telling me it's not supported. “PatchTST does not yet support historical exogenous variables”

@elephaint
Copy link
Contributor

PatchTST (the architecture) does not support additional exogenous inputs afaik, that's why the exception is raised. Usually if it is not supported by the original architecture we will not include it, as it may require us to substantially deviate from the original work (adding exogenous to an architecture is quite tricky).

There are many other options that may provide equal or better forecasting performance at lower computational cost if you need to use exogenous variables, e.g. NHITS, TSMixerx, BiTCN.

Hope this helps.

@deiping
Copy link

deiping commented Oct 21, 2024

Hello, sir. It seems that patchtst is inherently multivariate. Additionally, patchtst appears to perform well with short time series, as indicated by tslib.

@elephaint
Copy link
Contributor

Hello, sir. It seems that patchtst is inherently multivariate. Additionally, patchtst appears to perform well with short time series, as indicated by tslib.

This doesn't relate to the issue at hand: multivariate/univariate has nothing to do with a model being able to handle exogenous covariates.

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

No branches or pull requests

5 participants