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

[Feature request]: Add --extend, --shift Options To flepimop-calibrate #400

Open
TimothyWillard opened this issue Nov 15, 2024 · 1 comment
Labels
enhancement Request for improvement or addition of new feature(s). gempyor Concerns the Python core. high priority High priority. inference Concerns the parameter inference framework.

Comments

@TimothyWillard
Copy link
Contributor

TimothyWillard commented Nov 15, 2024

Label

enhancement, gempyor, inference

Priority Label

high priority

Is your feature request related to a problem? Please describe.

Updating forecasting configurations with new data is currently complex and relies on manual processes or elaborate scripts (e.g., modifying R scripts to adjust dates and fitting targets). This makes iterative updates cumbersome and error-prone, lacking a streamlined, automated workflow. See this slack thread for the original discussion: https://uncreturntocampus.slack.com/archives/CU0SBC2AC/p1731689410476909.

Is your feature request related to a new application, scenario round, pathogen? Please describe.

n/a

Describe the solution you'd like

Add two options to the flepimop-calibrate tool:

  1. --extend: Adjusts the end dates and fitting targets in the configuration file while incorporating new target data, and
  2. --shift: Offsets both start and end dates for recalibration.

Both options:

  • Reuse conserved parameters from the base configuration,
  • Transform output data into an updated configuration file for iterative use, and
  • Simplify forecasting workflows with a single command.
@TimothyWillard TimothyWillard added enhancement Request for improvement or addition of new feature(s). gempyor Concerns the Python core. high priority High priority. inference Concerns the parameter inference framework. labels Nov 15, 2024
@pearsonca
Copy link
Contributor

So roughly practically: on the first iteration, we run:

flepimop calibrate someconfig.yml

that yields the first set of outputs. The second invocation would be

flepimop calibrate someconfig.yml --extend="2 weeks" > config_2.yml

and subsequently would look iteratively like:

flepimop calibrate config_n.yml --extend="2 weeks" > config_n+1.yml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Request for improvement or addition of new feature(s). gempyor Concerns the Python core. high priority High priority. inference Concerns the parameter inference framework.
Projects
None yet
Development

No branches or pull requests

2 participants