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

Generates forcings when requested. #30

Open
sverhoeven opened this issue Sep 3, 2021 · 0 comments
Open

Generates forcings when requested. #30

sverhoeven opened this issue Sep 3, 2021 · 0 comments

Comments

@sverhoeven
Copy link
Member

The notebook generated by /pyewatercycle endpoint (#29) expects the forcings to be inside pararmeter set or already prepped in /mnt/data/forcing/<some forcing> directory. It would be nice if the endpoint could be passed properties which would generate forcings.

For wflow the prop could look like

forcing_options: {
   dataset:"ERA5",
   start_time: "1990-01-01T00:00:00Z",
   end_time: "1990-12-31T00:00:00Z",
   shape: "<some path to shape files>/Merrimack.shp",
   model_specific_options: {
       "dem_file": <somewhere where wflow pararmeter set is>/staticmaps/wflow_dem.map"),
   },
}

There are some problems to overcome:

  • map model.name to target_model. Propably with lower()
  • have central place for shape files so relatives paths can be used in Terria catalog item
  • have flexible definition of model_specific_options that works for supported models
  • dem_file can be found in parameter set or some where else. Need to decide which relative path to pass.
  • lisflood forcing generation still needs manual steps, see lisflood generate forcing needs an argument to run lisvap ewatercycle-lisflood#11
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

1 participant