Make data retrieval rules use their own minimal conda env #888
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 tosudo 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
envs/environment.yaml
.config.default.yaml
.doc/configtables/*.csv
.doc/release_notes.rst
is added.