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

Run of user guide notebook fails at wflow intialize #277

Closed
SarahAlidoost opened this issue Nov 29, 2021 · 5 comments
Closed

Run of user guide notebook fails at wflow intialize #277

SarahAlidoost opened this issue Nov 29, 2021 · 5 comments

Comments

@SarahAlidoost
Copy link
Member

SarahAlidoost commented Nov 29, 2021

I try to run the user guide notebook on snellius, see the notebook in this PR. The cell running model_instance.initialize(cfg_file) took a long time to complete, wflow version="2020.1.1". The log file can be found here /scratch-shared/ewatercycle/wflow_20211129_105649/run_default/wflow.log. There, an error is reported as: wf_netcdfio - ERROR - EPGS not converted correctly: EPSG:4326. Is the GDAL_DATA environment variable set correctly?

@SarahAlidoost
Copy link
Member Author

see this comment by @sverhoeven .

@sverhoeven
Copy link
Member

As a workaround we could use wflow version="2020.1.2", but it would be nice to fix wflow version="2020.1.1" image as well.

@Peter9192
Copy link
Collaborator

So can this be fixed by explicitly setting the GDAL_DATA env variable somewhere?

@sverhoeven
Copy link
Member

Yes it can, by setting in the Dockerfile like was done for the 2020.1.2 Docker image at https://github.com/eWaterCycle/grpc4bmi-examples/blob/d9291c11de3859248f3926aa5e2aa0f987c9afdf/wflow/Dockerfile#L13

SarahAlidoost added a commit that referenced this issue Dec 1, 2021
* re-run the user guide notebook on snellius

* change wflow version from 1 to 2 due to issue #277
@jeromaerts
Copy link
Member

jeromaerts commented Jan 17, 2022

I have the exact same problem with the wflow 2020.1.3 container while using singularity. @sverhoeven was your fix implemented when building the 2020.1.3 image?

@BSchilperoort BSchilperoort closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2024
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

5 participants