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

support for forecast issue time #235

Open
edvin-svk opened this issue Mar 22, 2024 · 1 comment
Open

support for forecast issue time #235

edvin-svk opened this issue Mar 22, 2024 · 1 comment

Comments

@edvin-svk
Copy link

Hello!
Is there support for fitting a model with a certain issue/creation time n time steps before the prediction target window? I.e. I want to make the prediction at time t for time steps [t+12, t+12+24] (make prediction at at lunch time for the next days 24 hours).

I could of course extend forecast_length to go far enough into the future, but then I'd like the validation to ignore the first 12 time steps of this forecast length.

@winedarksea
Copy link
Owner

Assuming I understand correctly, your best plan is to resample the data to a 12 hour frequency instead of hourly frequency. Specify frequency = '12h' or resample before passing into the model. Because yes, it definitely helps focus the model only on the points you care about rather than everything else.

Another option that can help a little is to focus on using the 'ewmae_weighting' in the metric_weighting. This doesn't ignore the first n points but it does weight the accuracy to the end more than the beginning.

No, I don't have support for specifying a 'custom' number of required steps ahead. This is because some models use a forward rolling approach to forecasting (n+1 used for n+2 which is used for n+3, etc) which means you can't really skip steps easily.

I could add per timestep weighting to the metrics, if you really think that would help your use case.

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