-
Notifications
You must be signed in to change notification settings - Fork 0
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
More pre-installed parameter sets #86
Comments
pcrglobwb global parameter sets are already downloaded to HPC Cloud machine, available under One wflow example parameter set is available under |
Lisflood parameter sets are available on Cartesius: |
List of pre-installed parameter sets now extended to: lisflood_fraser/ But not all are added to |
Now, the following parameter sets are available.
More can be added by putting custom .ini files in the pcrglob_global directory and adding them to the ewatercycle.yaml config file. |
Done for the tech example notebooks Leaving this open because we might want to add even more for the comparison study. |
I copied the files to dcache as [email protected] with cd /mnt/data
rclone copy lorentz-models dcache:lorentz-models;rclone copy examples dcache:examples;rclone copy forcing dcache:forcing;rclone copy parameter-sets dcache:parameter-sets |
We might want to deprecate the examples folder there. |
Currently, we only have the three example cases as pre-installed parameter sets. This is a good set for anyone installing the ewatercycle platform from scratch.
However, in the ewatercycle project, we use more parameter sets. It would be good to also pre-install these parameter sets on the infrastructure we host, so anyone contributing to the ewatercycle project with access to our resources can just use them.
This currently includes:
and uncalibrated) parameter sets for Wflow (uncalibrated way bigger!)and uncalibrated) parameter set for Lisflood (only found 1 version)They should be available under
/mnt/data/parameter-sets
and configured in/etc/ewatercycle.yaml
The text was updated successfully, but these errors were encountered: