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

Question about input_data of forecast_on_df method #186

Open
minelab-112stdnt-No7 opened this issue Nov 13, 2024 · 1 comment
Open

Question about input_data of forecast_on_df method #186

minelab-112stdnt-No7 opened this issue Nov 13, 2024 · 1 comment

Comments

@minelab-112stdnt-No7
Copy link

When using forecast_on_df, the input data is required to have three columns: unique_id, ds, and value_name. In the ds column, I tried storing data as integers representing the elapsed seconds or days, instead of using timestamp data of the datetime type.

image

However, this led to an error during the forecasting process, with the error message indicating that the ds column must contain timestamp data.

image
image

I would like to know if there is a way to make forecast_on_df work with data types other than timestamps in the ds column, or if I should consider using a different forecasting method.

@rajatsen91
Copy link
Collaborator

Hi, for your use case the forecast() method with freq=0 might be a better fit.

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