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

Don't copy forcing for Hype model #6

Open
sverhoeven opened this issue Jun 20, 2022 · 0 comments
Open

Don't copy forcing for Hype model #6

sverhoeven opened this issue Jun 20, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@sverhoeven
Copy link
Member

At the moment the forcings are copied to the working directory at https://github.com/eWaterCycle/ewatercycle/blob/107db173115cd35bfac42b5aaac9842580b9b45a/src/ewatercycle/models/hype.py#L123

Hype can be configured with forcingdir in info.txt, see http://www.smhi.net/hype/wiki/doku.php?id=start:hype_file_reference:info.txt
By setting forcingDir and mounting the forcing dir into the container we could make the ewatercycle.models.Hype.setup() method quicker and more similar to other models.

We should check that all files the model sees as forcing files are actually in the ewatercycle forcing object. If not then model could die due to misplaced files.

@sverhoeven sverhoeven added the enhancement New feature or request label Jun 20, 2022
@BSchilperoort BSchilperoort transferred this issue from eWaterCycle/ewatercycle Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant