Scenario management

[FabianHofmann]

From release notes:

PyPSA-EUR now supports the simultaneous execution of multiple scenarios. For this purpose, a scenarios.yaml file has been introduced which contains customizable scenario names with corresponding configuration overrides. To enable it, set the run: scenarios: key to True and define the scenario names to run under run: name: in the configuration file. The latter must be a subset of toplevel keys in the scenario file.

Checklist

• I tested my contribution locally and it seems to work fine.
• Code and workflow changes are sufficiently documented.
• Changed dependencies are added to envs/environment.yaml.
• Changes in configuration options are added in all of config.default.yaml.
• Changes in configuration options are also documented in doc/configtables/*.csv.
• A release note doc/release_notes.rst is added.

[FabianHofmann]

@fneum if you want you can already have a look, I will test it further locally for my project.

[FabianHofmann]

Note: Sweeping across years also works with this. For example using the scenario.yaml

network2013:
  snapshots:
    start: "2013-01-01"
    end: "2014-01-01"
    inclusive: 'left'


network2019:
  snapshots:
    start: "2019-01-01"
    end: "2020-01-01"
    inclusive: 'left'

  renewable:
    onwind:
      cutout: europe-2019-era5
    offwind-ac:
      cutout: europe-2019-era5
    offwind-dc:
      cutout: europe-2019-era5
    solar:
      cutout: europe-2019-era5
    hydro:
      cutout: europe-2019-era5

will create two resource and result folders with distinct years.

[fneum]

Note: Sweeping across years also works with this. For example using the scenario.yaml

Oh, I am excited about this!

[lindnemi]

config_value= should probably be called config_key= in this line to avoid confusion

[fneum]

merged via 184f3a0