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

UN demand data inputs removed automatically for each run of build_base_energy_totals #1298

Open
2 tasks
ekatef opened this issue Jan 15, 2025 · 0 comments
Open
2 tasks
Labels
bug Something isn't working

Comments

@ekatef
Copy link
Member

ekatef commented Jan 15, 2025

Checklist

  • I am using the current main branch or the latest release. Please indicate.
  • I am running on an up-to-date pypsa-earth environment. Update via conda env update -f envs/environment.yaml.

Describe the Bug

It appears that an explicit specification of the the UN data directory as snakemake output needed to improve stability the workflow #1279 had also some side effects.

If build_base_energy_totals is being executed Snakemake first removes all the outputs including data/demand/unsd/data/. If demand_data:update_data is false the execution is being terminated, otherwise the UN demand files are being downloaded again.
It feels like the behaviour is linked with Snakemake logic, and a way to fix may be to breakdown build_base_energy_totals on the data retrieval and the computational parts.

@ekatef ekatef added the bug Something isn't working label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant