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
# PyPSA-DE - Hochaufgelöstes, sektorengekoppeltes Modell des deutschen Energiesystems
2
2
3
-
Dieses Repository enthält das Gesamtsystemmodell PyPSA-DE für das Kopernikus-Projekt Ariadne, basierend auf der Toolbox PyPSA und dem Datensatz PyPSA-Eur. Das Modell bildet Deutschland mit hoher geographischer Auflösung, mit voller Sektorenkopplung und mit Integration in das europäische Energiesystem ab.
3
+
PyPSA-DE ist ein sektorengekoppeltes Energiesystem-Modell auf Basis der Toolbox [PyPSA](https://github.com/PyPSA/pypsa) und des europäischen Modells [PyPSA-Eur](https://github.com/PyPSA/pypsa-eur). Der PyPSA-DE Workflow modelliert das deutsche Energiesystem mit deutschlandspezifischen Datensätzen (MaStR, Netzentwicklungsplan,...) im Verbund mit den direkten Stromnachbarn sowie Spanien und Italien. Der Ausbau und der Betrieb von Kraftwerken, des Strom- und Wasserstoffübertragunsnetzes und die Energieversorgung aller Sektoren werden dann in einem linearen Optimierungsproblem gelöst, mit hoher zeitlicher und räumlicher Auflösung. PyPSA-DE wurde im Rahmen des Kopernikus-Projekts [Ariadne](https://ariadneprojekt.de/) entwickelt in dem Szenarien für ein klimaneutrales Deutschland untersucht werden, und spielt eine zentrale Rolle im Ariadne Szenarienreport, als Leitmodell für den Sektor Energiewirtschaft und als eines von drei Gesamtsystemmodellen.
4
+
5
+
# PyPSA-DE - High resolution, sector-coupled model of the German Energy System
6
+
7
+
PyPSA-DE is a sector-coupled energy system model based on the toolbox [PyPSA](https://github.com/PyPSA/pypsa) and the European model [PyPSA-Eur](https://github.com/PyPSA/pypsa-eur). It solves a linear optimization problem to simulate the electricty and hydrogen transmission networks, as well as supply, demand and storage in all sectors of the energy system in Germany and its neighboring countries, as well as Italy and Spain, with high spatial and temporal resolution. PyPSA-DE was developed in the context of the Kopernikus-Projekt [Ariadne](https://ariadneprojekt.de/en/), which studies scenarios of a carbon-neutral German economcy, and plays a decisive role in the upcoming Ariadne Szenarienreport, as reference model for the energy sector.
4
8
5
9
This repository contains the entire scientific project, including data sources and code. The philosophy behind this repository is that no intermediary results are included, but all results are computed from raw data and code.
You need `conda` or `mamba` to run the analysis. Using conda, you can create an environment from within which you can run the analysis:
10
16
11
-
conda env create -f envs/environment.yaml
17
+
```
18
+
conda env create -f envs/{os}-pinned.yaml
19
+
```
12
20
13
-
## For external users: Use config.public.yaml
21
+
Where `{os}` should be replaced with your operating system, e.g. for linux the command would be:
14
22
15
-
The default workflow configured for this repository assumes access to the internal Ariadne2 database. Users that do not have the required login details can run the analysis based on the data published during the [first phase of the Ariadne project](https://data.ece.iiasa.ac.at/ariadne/).
23
+
```
24
+
conda env create -f envs/linux-pinned.yaml
25
+
```
26
+
27
+
## Connecting to the Ariadne-Database
28
+
29
+
### For external users: Use config.public.yaml
30
+
31
+
The default workflow configured for this repository assumes access to the internal Ariadne2 database. The database will soon be publicly available. Until then, users that do not have the required login details can run the analysis based on the data published during the [first phase of the Ariadne project](https://data.ece.iiasa.ac.at/ariadne/).
16
32
17
33
This is possible by providing an additional config to the snakemake workflow. For every `snakemake COMMAND` specified in the instructions below, public users should use:
The additional config file specifies the required database, model, and scenario names for Ariadne1. If public users wish to edit the default scenario specifications, they should change `scenarios.public.yaml`instead of`scenarios.manual.yaml`. More details on using scenarios are given below.
39
+
The additional config file specifies the required database, model, and scenario names for Ariadne1. If public users wish to edit the default scenario specifications, they can do so by changing `scenarios.public.yaml`to`scenarios.manual.yaml`. More details on using scenarios are given below.
24
40
25
-
## For internal users: Provide login details
41
+
###For internal users: Provide login details
26
42
27
43
The snakemake rule `retrieve_ariadne_database` logs into the interal Ariadne IIASA Database via the [`pyam`](https://pyam-iamc.readthedocs.io/en/stable/tutorials/iiasa.html) package. The credentials for logging into this database have to be stored locally on your machine with `ixmp4`. To do this activate the project environment and run
28
44
@@ -51,8 +67,7 @@ To run the analysis use
51
67
52
68
snakemake ariadne_all
53
69
54
-
This will run all analysis steps to reproduce results. If computational resources on your local machine are limit you may decrease the number of cores by adding, e.g. `-c4` to the call.
55
-
70
+
This will run all analysis steps to reproduce results. If computational resources on your local machine are limited you may decrease the number of cores by adding, e.g. `-c4` to the call to get only 4 cores. For more option please refer to the [snakemake](https://snakemake.readthedocs.io/en/stable/) documentation.
56
71
57
72
## Repo structure
58
73
@@ -64,28 +79,45 @@ This will run all analysis steps to reproduce results. If computational resource
64
79
*`resources`: place for intermediate/processing data for the workflow (does not exist initially)
65
80
*`results`: will contain all results (does not exist initially)
66
81
*`logs` and `benchmarks`
67
-
* The `Snakefile` contains the snakemake workflow
82
+
* The `Snakefile` contains the PyPSA-DE specific snakemake workflow
83
+
84
+
## Differences to PyPSA-EUR
68
85
69
-
## Some notable differences to PyPSA-EUR
86
+
PyPSA-DE is a softfork of PyPSA-EUR. As such, large parts of the functionality are similar, and the [documentation](https://pypsa-eur.readthedocs.io/en/latest/) of PyPSA-Eur is a good starting point to get acquainted with the model. On topf of that, PyPSA-DE adds several data sources and workflow steps that improve the representation of the German Energy System. Below is a non-conclusive list of the most important changes.
70
87
88
+
- Default resolution of 16 regions in Germany and 13 region for neighboring countries
89
+
- 10 pre-defined scenarios (1 Current Policies, 3 Net-Zero Scenarios (Balanced, Focus H2, Focus Electricity), 2 Demand Variations based on the Balanced Scenario, 4 Demand Variations Based on the Current Policies Scenario)
71
90
- Specific cost assumption for Germany:
91
+
72
92
- Gas, Oil, Coal prices
73
93
- electrolysis and heat-pump costs
74
-
- Infrastructure costs according to the Netzentwicklungsplan 23 (NEP23)
94
+
- Infrastructure costs [according to the Netzentwicklungsplan](https://github.com/PyPSA/pypsa-ariadne/pull/193) 2021 and 2023
75
95
- option for pessimstic, mean and optimistic cost development
76
-
- Transport and Industry demands as well as heating stock imported from the sectoral models in the Ariadne consortium
96
+
- Transport and Industry demands as well as heating stock imported from the sectoral models in the Ariadne consortium ([Aladin](https://ariadneprojekt.de/modell-dokumentation-aladin/), [REMOD](https://ariadneprojekt.de/modell-dokumentation-remod/), [FORECAST](https://ariadneprojekt.de/modell-dokumentation-forecast/) and [REMIND](https://ariadneprojekt.de/modell-dokumentation-remind/))
77
97
- More detailed data on CHPs in Germany
78
-
- Option for building the German Wasserstoffkernnetz
79
98
- The model has been validated against 2020 electricity data for Germany
80
99
- National CO2-Targets according to the Klimaschutzgesetz
81
100
- Additional constraints that limit maximum capacity of specific technologies
82
-
- Import constraints
101
+
- Import constraints on Efuels, hydrogen and electricity
83
102
- Renewable build out according to the Wind-an-Land, Wind-auf-See and Solarstrategie laws
84
-
- A comprehensive reporting module that exports Capacity Expansion, Primary/Secondary/Final Energy, CO2 Emissions per Sector, Trade, Investments, ...
103
+
- A comprehensive reporting module that exports Capacity Expansion, Primary/Secondary/Final Energy, CO2 Emissions per Sector, Trade, Investments, and more.
85
104
- Plotting functionality to compare different scenarios
86
-
- Electricity Network development until 2030 (and for AC beyond) according to the Netzentwicklungsplan
87
-
- Offshore development until 2030 according to the Offshore Netzentwicklungsplan
105
+
- Electricity Network development until 2030 (and for AC beyond) according to the NEP23
106
+
- Offshore development until 2030 according to the Offshore NEP23
88
107
- Hydrogen network development until 2028 according to the Wasserstoffkernnetz. PCI / IPCEI projects for later years are included as well.
108
+
-`costs:horizon` - specify if technology costs are expected to follow an `optimistic, mean` or `pessimistic` trajectory
109
+
110
+
## New Config Options
111
+
112
+
-`iiasa_database` - interaction with IIASA database. Specify a database, and `leitmodelle` for demand and co2 emissions data in specific sectors
113
+
-`wasserstoff_kernnetz` - configure which parts of the Wasserstoff Kernnetz should be included in the model
114
+
-`new_decentral_fossil_boiler_ban` - specify in which country and which years to ban fossil boilers
115
+
-`coal_generation_ban` - specify in which country and which years to ban electricity generation from coal
116
+
-`nuclear_generation_ban` - specify in which country and which years to ban electricity generation from nuclear
117
+
-`first_technology_occurrence` - specify the year form which on specific technologies are available
118
+
-`solving:constraints` - specify PyPSA-DE specific limits, e.g. on capacity, trade and generation
119
+
-`co2_budget_DE_source` specify the carbon trajectory for Germany: Following the projections of the Umweltbundestamt (`UBA`) or targeting net zero with the Klimaschutzgesetz(`KSG`)
120
+
-`costs:NEP` and `costs:transmission` - specify which year of the Netzentwicklungsplan should be used as basis for the transmission line costs (`2021,2023`) and if new HVDC links should be built with `overhead` or `underground` cables
0 commit comments