Previously, the costs for 2030 were stored in the repo ìn the data/ folder. These costs are now removed and replaced by an automized download depending on the wildcard planning_horizon. The version of the cost data can be adjusted in the config.yaml and is currently set to the latest release https://github.com/PyPSA/technology-data/releases/tag/v0.6.2.
Checklist
[x] I tested my contribution locally and it seems to work fine.
[x] Code and workflow changes are sufficiently documented.
[x] Newly introduced dependencies are added to envs/environment.yaml and envs/environment.docs.yaml.
[x] Changes in configuration options are added in all of config.default.yaml, config.tutorial.yaml, and test/config.test1.yaml.
[ ] Changes in configuration options are also documented in doc/configtables/*.csv and line references are adjusted in doc/configuration.rst and doc/tutorial.rst.
[ ] A note for the release notes doc/release_notes.rst is amended in the format of previous release notes, including reference to the requested PR.
Changes proposed in this Pull Request
Previously, the costs for 2030 were stored in the repo ìn the
data/
folder. These costs are now removed and replaced by an automized download depending on the wildcardplanning_horizon
. The version of the cost data can be adjusted in theconfig.yaml
and is currently set to the latest release https://github.com/PyPSA/technology-data/releases/tag/v0.6.2.Checklist
envs/environment.yaml
andenvs/environment.docs.yaml
.config.default.yaml
,config.tutorial.yaml
, andtest/config.test1.yaml
.doc/configtables/*.csv
and line references are adjusted indoc/configuration.rst
anddoc/tutorial.rst
.doc/release_notes.rst
is amended in the format of previous release notes, including reference to the requested PR.