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

Make data retrieval rules use their own minimal conda env #888

Merged
merged 2 commits into from Jan 23, 2024

Conversation

koen-vg
Copy link
Contributor

@koen-vg koen-vg commented Jan 23, 2024

I usually use the default snakemake options for when to re-run rules; including when the software environment changes. This means, however, that even data-retrieval rules would re-run when changing some dependency version in environment.yaml. Such re-runs have become especially painful now that the output files from these data retrieval rules are being marked as protected: this prevents the rule from re-running, and I have to sudo rm -rf the databundles! Not great.

The present PR just creates a separate, minimal conda env for the retrieval rules. Just a quality-of-life improvement.

(And it seems some snakefmt fixed have sneaked their way in.)

Checklist

  • I tested my contribution locally and it seems to work fine.
  • Code and workflow changes are sufficiently documented.
  • Changed dependencies are added to envs/environment.yaml.
  • Changes in configuration options are added in all of config.default.yaml.
  • Changes in configuration options are also documented in doc/configtables/*.csv.
  • A release note doc/release_notes.rst is added.

koen-vg and others added 2 commits January 23, 2024 16:27
This means that the main conda environment can be changed for
development purposes without necessitating the re-running of data
retrieval due to software environment change by default.
@fneum
Copy link
Member

fneum commented Jan 23, 2024

Excellent, thanks @koen-vg! I will also take care of the #886 now.

@fneum fneum merged commit fb2e9da into PyPSA:master Jan 23, 2024
1 of 5 checks passed
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

Successfully merging this pull request may close these issues.

None yet

2 participants