This PR distributes a config.default.yaml and copies it to config.yaml for individual scenario setting. This way, we can keep a running default yaml but still make our own personal scenario explorations without changing major things.
Note: previously we had a very strict limit on RE potentials, which is now removed.
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.
[x] Changes in configuration options are also documented in doc/configtables/*.csv and line references are adjusted in doc/configuration.rst and doc/tutorial.rst.
[x] 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.
Closes # (if applicable).
Changes proposed in this Pull Request
This PR distributes a
config.default.yamland copies it toconfig.yamlfor individual scenario setting. This way, we can keep a running default yaml but still make our own personal scenario explorations without changing major things.Note: previously we had a very strict limit on RE potentials, which is now removed.
Checklist
envs/environment.yamlandenvs/environment.docs.yaml.config.default.yaml,config.tutorial.yaml, andtest/config.test1.yaml.doc/configtables/*.csvand line references are adjusted indoc/configuration.rstanddoc/tutorial.rst.doc/release_notes.rstis amended in the format of previous release notes, including reference to the requested PR.