You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running on an up-to-date pypsa-usa environment. Update via conda env update -f envs/environment.yaml
The Issue
Running sector studies causes (in particular) the build_demand rule to be much heavier than the electrical counterpart. This often (at least on my computer) causes rules to fail with the error along the lines of:
/usr/bin/bash: line 1: 14318 Killed /home/trevor/miniforge3/envs/pypsa-usa/bin/python3.11 /home/trevor/master/pypsa-usa/workflow/.snakemake/scripts/tmp1zwbgps2.build_demand.py
This is just a resource allocation issue, and rerunning the workflow will eventually get past this.
Within the snakemake rules, the resources need to be updated to use the sector wildcard and determine appropriate resource limits.
Steps To Reproduce
Turn on sector studies
Run snakemake -j32 (or similar)
Expected Behavior
No response
Error Message
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
I don't think the resource allocation (mem_mb / threads ) are actually used when you run it locally, snakemake only uses those for cluster runs. I think to deal with this you should run with -j1 --cores all to reduce the number of jobs running at once, and with all cores being used.
Im gonna reopen this, as I believe memory allocation is used when run locally? I can't find specifically in the docs where it says one way or another (closest I can find is here). But if when running locally on my computer, if I monitor memory usage, I can see more memory being used if I relax the limits.
Checklist
master
branchpypsa-usa
environment. Update viaconda env update -f envs/environment.yaml
The Issue
Running sector studies causes (in particular) the
build_demand
rule to be much heavier than the electrical counterpart. This often (at least on my computer) causes rules to fail with the error along the lines of:This is just a resource allocation issue, and rerunning the workflow will eventually get past this.
Within the snakemake rules, the resources need to be updated to use the sector wildcard and determine appropriate resource limits.
Steps To Reproduce
snakemake -j32
(or similar)Expected Behavior
No response
Error Message
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: