Merge pypsa eur sec #484
Merge pypsa eur sec #484
Conversation
test configs: reduce to relative changes CI: use snakemake --configfile options
Integrate linopy as solver framework
Snakefile: retrieve data bundle from pypsaeur function
automatically retrieve technology-data, no git clone
build sequestration: fix input for new snakemake versions
compatibility with technology-data v0.5
|
I had a rough look at the docs and I think they are nicely structured, thanks @fneum! I would be fine with merging at this point. Bug fixing can be done anyway in the new master. Sidenote: I think it would be good to introduce a |
set default share_cutout: True
… merge-pypsa-eur-sec
for more information, see https://pre-commit.ci
|
looks really great @fneum, @FabianHofmann . I had a look at the documentation and tried one electricity only, one sector-coupled and one myopic run, all worked nice and smoothly! |
for more information, see https://pre-commit.ci
… merge-pypsa-eur-sec
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
… merge-pypsa-eur-sec
for more information, see https://pre-commit.ci
|
According to our todo list, the only thing missing is the final releases of pypsa-eur(-sec) before merging. However looking at the changes in pypsa-eur since the release, none of it is functional (version fixes, tqdm, cluster wildcard). So I don't even know whether this is necessary. So, I am happy with merging as is anytime :) |
|
Alright, I agree that we don't need new independent releases before merging because 0.7.0 was very recent and because no functional changes were made since then. Ok, since @lisazeyen, @FabianHofmann, @fneum are happy, and @nworbmot reviewed the docs, let's move ahead! |
|
Whoop!! |
Closes #463
Closes #450
Closes #613
Closes #612
Checklist