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
Copy file name to clipboardExpand all lines: README.md
+14-18Lines changed: 14 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,9 @@ This repository contains the entire scientific project, including data sources a
6
6
7
7
## Getting ready
8
8
9
-
You need conda or [mamba](https://mamba.readthedocs.io/en/latest/) to run the analysis. Using mamba, you can create an environment from within you can run it:
9
+
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
10
11
-
mamba env create -f environment.yaml
11
+
conda env create -f envs/environment.yaml
12
12
13
13
## For external users: Use config.public.yaml
14
14
@@ -40,40 +40,33 @@ To switch between internal and public use, the command `ixmp4 logout` may be nec
40
40
41
41
Before running any analysis with scenarios, the rule `build_scenarios` must be executed. This will create the file `config/scenarios.automated.yaml` which includes input data and CO2 targets from the IIASA Ariadne database as well as the specifications from the manual scenario file. [This file is specified in the default config.yaml via they key `run:scenarios:manual_file` (by default located at `config/scenarios.manual.yaml`)].
Note that the hierarchy of scenario files is the following: `scenarios.automated.yaml` > (any `explicitly specified --configfiles`) > `config.yaml `> `config.default.yaml `Changes in the file `scenarios.manual.yaml `are only taken into account if the rule `build_scenarios` is executed.
49
49
50
-
For the first run, open config.yaml and set
50
+
To run the analysis use
51
51
52
-
enable:
53
-
retrieve: true # set to false once initial data is retrieved
54
-
retrieve_cutout: true # set to false once initial data is retrieved
52
+
snakemake ariadne_all
55
53
56
-
and then run from main repository
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.
57
55
58
-
snakemake -call
59
-
60
-
This will run all analysis steps to reproduce results.
61
-
62
-
To generate a PDF of the dependency graph of all steps `build/dag.pdf` run:
63
-
64
-
snakemake -c1 --use-conda -f dag
65
56
66
57
## Repo structure
67
58
68
59
*`config`: configuration files
69
60
*`ariadne-data`: Germany specific data from the Ariadne project
70
-
*`workflow`: contains the Snakemake workflow, including the submodule PyPSA-Eur and specific scripts for Germany
61
+
*`scripts`: contains the Python scripts for the workflow, the Germany specific code needed to run this repo is contained in `scripts/pypsa-de`
71
62
*`cutouts`: very large weather data cutouts supplied by atlite library (does not exist initially)
72
63
*`data`: place for raw data (does not exist initially)
73
64
*`resources`: place for intermediate/processing data for the workflow (does not exist initially)
74
65
*`results`: will contain all results (does not exist initially)
66
+
*`logs` and `benchmarks`
67
+
* The `Snakefile` contains the snakemake workflow
75
68
76
-
## Differences to PyPSA-EUR
69
+
## Some notable differences to PyPSA-EUR
77
70
78
71
- Specific cost assumption for Germany:
79
72
- Gas, Oil, Coal prices
@@ -90,6 +83,9 @@ To generate a PDF of the dependency graph of all steps `build/dag.pdf` run:
90
83
- Renewable build out according to the Wind-an-Land, Wind-auf-See and Solarstrategie laws
91
84
- A comprehensive reporting module that exports Capacity Expansion, Primary/Secondary/Final Energy, CO2 Emissions per Sector, Trade, Investments, ...
92
85
- 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
88
+
- Hydrogen network development until 2028 according to the Wasserstoffkernnetz. PCI / IPCEI projects for later years are included as well.
0 commit comments