-
Notifications
You must be signed in to change notification settings - Fork 212
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
Error in build_cutout for Ukraine #669
Comments
@ekatef Hazem conveyed that you might solve this issue easily. |
Hi @Eddy-JV, previously we had some geometry-related issues but they all are (hopefully :) ) fixed now. The error you are experiencing has not been seen yet. Thanks a lot for reporting! My feeling is that it can be caused by some dependencies conflict as state this and this SO threads. I'd suggest to build a fresh environment to be sure that it doesn't contain any potentially conflicting dependencies. (Be sure please to keep your current environment as a back-up) |
That's surprising. I've run it for the world recently with no problems.
|
Update: the same issue appears for different areas of the world (Oceania and Nigeria, for example) and can be fixed by downgrade of Generally, such HDF5-DIAG warnings are known in the upstream packages (e.g. there is a discussion in this xarray issue) and are being fixed now. So, the issue we are facing can be probably resolved soon thanks to this work |
Is this still relevant? we should have earth coverage and packages have improved right? |
Checklist
main
branch or the latest release. Please indicate.pypsa-earth
environment. Update viaconda env update -f envs/environment.yaml
.Describe the Bug
When running the following full workflow for Ukraine:
snakemake -j 8 solve_all_networks
, I get the first shown error below whenbuilding_cutout.py
. The problem comes when saving the cutout.nc file. Then the workflow freezes at step 3 of 15 with @(20%).Previously to that, I get also a Runtimewarning when executing
build_shapes.py
. The warning is shown below in the second bash window. Could that be the source of the problem?N.B.: The only changes to the config.yaml file are:
Error Message
If applicable, paste any terminal output to help illustrating your problem.
In some cases it may also be useful to share your list of installed packages:
conda list
.The text was updated successfully, but these errors were encountered: