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
Switch model to use only public version of database (#81)
* new names for the scenarios
* delete public config
* not used in pypsa-de
* discontinue fallback_reference_scenario
* hard-code 2020 values from internal db
* remove unused code
* simplify readme
* whitespace
* remove unused code
* convert everything to MWh
* convert to Mwh instead of Gj
* fix pandas warning
* rename prefix
* fix empty plot
* fix overlooked conversion from Joule
* fix mobility demand
* fix rounding error in exporter
* increased tolerance for comparison
* switch to Mix value from steel production from Forecast 2020
* more correction of hardcoded steel values
* bump version
* add changes
---------
Co-authored-by: JulianGeis <JulianGeis@gmx.net>
Copy file name to clipboardExpand all lines: README.md
-32Lines changed: 0 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,42 +24,11 @@ Where `{os}` should be replaced with your operating system, e.g. for linux the c
24
24
conda env create -f envs/linux-pinned.yaml
25
25
```
26
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/).
32
-
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 can do so by changing `scenarios.public.yaml` to `scenarios.manual.yaml`. More details on using scenarios are given below.
40
-
41
-
### For internal users: Provide login details
42
-
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
44
-
45
-
```
46
-
ixmp4 login <username>
47
-
```
48
-
49
-
You will be prompted to enter your `<password>`.
50
-
51
-
Caveat: These credentials are stored on your machine in plain text.
52
-
53
-
To switch between internal and public use, the command `ixmp4 logout` may be necessary.
54
-
55
27
## Run the analysis
56
28
57
29
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 config.de.yaml via they key `run:scenarios:manual_file` and located at `config/scenarios.manual.yaml` by default].
Note that the hierarchy of scenario files is the following: `scenarios.automated.yaml` > (any `explicitly specified --configfiles`) > `config.de.yaml `> `config.default.yaml `Changes in the file `scenarios.manual.yaml `are only taken into account if the rule `build_scenarios` is executed.
65
34
@@ -88,7 +57,6 @@ PyPSA-DE is a softfork of PyPSA-EUR. As such, large parts of the functionality a
88
57
- Default resolution of 16 regions in Germany and 13 region for neighboring countries
89
58
- 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)
90
59
- Specific cost assumption for Germany:
91
-
92
60
- Gas, Oil, Coal prices
93
61
- electrolysis and heat-pump costs
94
62
- Infrastructure costs [according to the Netzentwicklungsplan](https://github.com/PyPSA/pypsa-ariadne/pull/193) 2021 and 2023
0 commit comments