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.

Sign up for GitHub

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

Jump to bottom

add forecast_date as a first-class part of the recipe object #380

Closed
dsweber2 opened this issue Sep 13, 2024 · 1 comment · Fixed by #433
Closed

add forecast_date as a first-class part of the recipe object #380

dsweber2 opened this issue Sep 13, 2024 · 1 comment · Fixed by #433

Comments

@dsweber2
Copy link
Contributor

Currently the forecast date is scattered across several functions. After #370, we should include it as a part of recipe construction in the first place, so we don't have multiple places where it might be added that might contradict eachother.
@dajmcdon
Copy link
Contributor

@dsweber2 Do you have an implementation of this somewhere? I think it would be helpful for the step_climate_predictor() implementation.

@dajmcdon dajmcdon mentioned this issue Jan 31, 2025
Merged
5 tasks
@dajmcdon dajmcdon linked a pull request Jan 31, 2025 that will close this issue
380 add forecast date recipe #433
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

380 add forecast date recipe cmu-delphi/epipredict
2 participants
@dsweber2 @dajmcdon