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

How to add future covariates #24

Open
Weidong725 opened this issue May 17, 2024 · 11 comments
Open

How to add future covariates #24

Weidong725 opened this issue May 17, 2024 · 11 comments

Comments

@Weidong725
Copy link

My task is to carry out power load forecasting, the data is one data point per 15min (96 time points a day), I also have temperature data in the same format.After reading your source code, I found that the input have x_enc, x_mark_enc, but I want to use the historical load and temperature data of 480 points (5 days), combined with the forecast temperature of 96 points in the future, to predict the load of 96 points in the future.I would like to ask you how to add future variables to network.

@kwuking
Copy link
Owner

kwuking commented May 17, 2024

Thank you sincerely for your interest in our work and for posing such an insightful question. Our TimeMixer model is designed with the flexibility to seamlessly integrate future known features as covariates into the forecasting process. To achieve this, one would need to adjust the future_multi_mixing module to include x_mark_dec as part of the temporal embedding within the prediction framework. Your suggestion is highly valued, and in response, I am committed to releasing an updated version of our model that incorporates this functionality in the near future.

@Weidong725
Copy link
Author

Thank you very much for your answer. Could you remind me after the update?

@kwuking
Copy link
Owner

kwuking commented May 17, 2024

Thank you very much for your answer. Could you remind me after the update?

Upon completion of the update, we will promptly notify you.

@Weidong725
Copy link
Author

Weidong725 commented May 21, 2024

Besides, I have one more question. Taking my above task as an example, when forecasting power load, should we put the historical temperature data into x_enc or x_mark_enc?

  1. If the historical temperature and load are put into the x_enc, whether to turn off the channel independently.
  2. If the temperature and the daily type code are put into the x_mark_enc together, is it reasonable? which embedding method is more appropriate for this case?

@kwuking
Copy link
Owner

kwuking commented May 23, 2024

Thank you very much for your answer. Could you remind me after the update?

Hi, we have updated the code and released a new version to support future feature prediction. You can refer to the introduction in the README.

@kwuking
Copy link
Owner

kwuking commented May 23, 2024

Besides, I have one more question. Taking my above task as an example, when forecasting power load, should we put the historical temperature data into x_enc or x_mark_enc?

  1. If the historical temperature and load are put into the x_enc, whether to turn off the channel independently.
  2. If the temperature and the daily type code are put into the x_mark_enc together, is it reasonable? which embedding method is more appropriate for this case?
  1. If you want the model to learn the relationship between the two, it is necessary to disable channel independence.

  2. Obviously, both methods are feasible. If you put the temperature into x_enc, we will learn the variable relationship between it and the load. If you put it into x_mark_enc, we will use it as a future-known covariate to assist in prediction. Both methods are viable; it depends on our modeling approach and the actual results. You can try both, which might require slight modifications to the code to adapt to your scenario.

@Weidong725
Copy link
Author

Thank you for your patient recovery. I'm ready to experiment with my task on the new version.

@qq234567890lyj
Copy link

你好,想问一下,复现这个代码需要改什么参数不,我这边复现出现问题了,想请教请教谢谢

@kwuking
Copy link
Owner

kwuking commented Jul 1, 2024

你好,想问一下,复现这个代码需要改什么参数不,我这边复现出现问题了,想请教请教谢谢

你好,看到了你的问题了,是否可以提供下具体的日志信息,以及执行的脚本和数据集的内容。

@wtt6668888
Copy link

在执行loss = criterion(outputs, batch_y)出现RuntimeError: The size of tensor a (96) must match the size of tensor b (144) at non-singleton dimension 1。就是在ETTh1数据集上执行的,还想请问一下这个模型可以利用多变量预测多变量吗?我的任务是一个时间点有ABC3个测量值,ABC之间是有联系的,之后预测ABC三个值,不知这个模型应当如何设置来预测呢?

@qq234567890lyj
Copy link

qq234567890lyj commented Sep 11, 2024 via email

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

4 participants