bjoern/pypsa-eur
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Replace _ with - in technology_data and prenetworks_brownfield

Browse Source 
Preferred by kubernetes.

Also updated the documentation accordingly.
This commit is contained in:
Tom Brown 2020-08-20 18:00:27 +02:00
parent 9b2fa7c140
commit d4368a966a
7 changed files with 51 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Snakefile
View File

@ -313,7 +313,7 @@ if config["foresight"] == "myopic":
costs=config['costs_dir'] + "costs_{}.csv".format(config['scenario']['planning_horizons'][0]),
cop_soil_total="resources/cop_soil_total_{network}_s{simpl}_{clusters}.nc",
cop_air_total="resources/cop_air_total_{network}_s{simpl}_{clusters}.nc"
output: config['results_dir'] + config['run'] + '/prenetworks_brownfield/{network}_s{simpl}_{clusters}_lv{lv}_{opts}_{sector_opts}_{co2_budget_name}_{planning_horizons}.nc'
output: config['results_dir'] + config['run'] + '/prenetworks-brownfield/{network}_s{simpl}_{clusters}_lv{lv}_{opts}_{sector_opts}_{co2_budget_name}_{planning_horizons}.nc'
wildcard_constraints:
planning_horizons=config['scenario']['planning_horizons'][0] #only applies to baseyear
threads: 1
@ -333,7 +333,7 @@ if config["foresight"] == "myopic":
cop_soil_total="resources/cop_soil_total_{network}_s{simpl}_{clusters}.nc",
cop_air_total="resources/cop_air_total_{network}_s{simpl}_{clusters}.nc"
output: config['results_dir'] + config['run'] + "/prenetworks_brownfield/{network}_s{simpl}_{clusters}_lv{lv}_{opts}_{sector_opts}_{co2_budget_name}_{planning_horizons}.nc"
output: config['results_dir'] + config['run'] + "/prenetworks-brownfield/{network}_s{simpl}_{clusters}_lv{lv}_{opts}_{sector_opts}_{co2_budget_name}_{planning_horizons}.nc"
threads: 4
resources: mem_mb=2000
script: "scripts/add_brownfield.py"
@ -342,7 +342,7 @@ if config["foresight"] == "myopic":
rule solve_network_myopic:
input:
network=config['results_dir'] + config['run'] + "/prenetworks_brownfield/{network}_s{simpl}_{clusters}_lv{lv}_{opts}_{sector_opts}_{co2_budget_name}_{planning_horizons}.nc",
network=config['results_dir'] + config['run'] + "/prenetworks-brownfield/{network}_s{simpl}_{clusters}_lv{lv}_{opts}_{sector_opts}_{co2_budget_name}_{planning_horizons}.nc",
costs=config['costs_dir'] + "costs_{planning_horizons}.csv",
config=config['summary_dir'] + '/' + config['run'] + '/configs/config.yaml'
output: config['results_dir'] + config['run'] + "/postnetworks/{network}_s{simpl}_{clusters}_lv{lv}_{opts}_{sector_opts}_{co2_budget_name}_{planning_horizons}.nc"

2
config.default.yaml
View File

@ -2,7 +2,7 @@ logging_level: INFO
results_dir: 'results/'
summary_dir: results
costs_dir: '../technology_data/outputs/'
costs_dir: '../technology-data/outputs/'
run: 'your-run-name' # use this to keep track of runs with different settings
foresight: 'overnight' #options are overnight, myopic, perfect (perfect is not yet implemented)

2
config.myopic.yaml
View File

@ -2,7 +2,7 @@ logging_level: INFO
results_dir: 'results/'
summary_dir: results
costs_dir: '../technology_data/outputs/'
costs_dir: '../technology-data/outputs/'
run: 'your-run-name' # use this to keep track of runs with different settings
foresight: 'myopic' #options are overnight, myopic, perfect (perfect is not yet implemented)

6
doc/index.rst
View File

@ -116,15 +116,17 @@ Documentation
installation
**Myopic transition path**
**Foresight options**
* :doc:`overnight`
* :doc:`myopic`
.. toctree::
:hidden:
:maxdepth: 1
:caption: Myopic transition path
:caption: Foresight options
overnight
myopic
**References**

23
doc/installation.rst
View File

@ -7,8 +7,8 @@ Installation
The subsequently described installation steps are demonstrated as shell commands, where the path before the ``%`` sign denotes the
directory in which the commands following the ``%`` should be entered.
Install PyPSA-Eur
=================
Install PyPSA-Eur and its data
==============================
First install `PyPSA-Eur <https://github.com/PyPSA/pypsa-eur>`_ and all
its dependencies. Clone the repository:
@ -21,6 +21,16 @@ its dependencies. Clone the repository:
then download and unpack all the PyPSA-Eur data files.
Clone technology-data repository
================================
Create a parallel directory for the technology costs and other assumptions:
.. code:: bash
projects % git clone git@github.com:PyPSA/technology-data.git
Clone PyPSA-Eur-Sec repository
==============================
@ -61,7 +71,10 @@ To download and extract it on the command line:
Set up the default configuration
================================
First make your own copy of the ``config.yaml``:
First make your own copy of the ``config.yaml``. For overnight
scenarios, use ``config.default.yaml``. For a pathway optimization
with myopic foresight (which is still experimental), use
``config.myopic.yaml``. For example:
.. code:: bash
@ -81,7 +94,7 @@ To run the full optimization with your settings:
.. code:: bash
projects/pypsa-eur-sec % snakemake
projects/pypsa-eur-sec % snakemake -j1
Warning: you may need a computer cluster for this (with e.g. 10-100 GB of RAM
and several processors).
@ -90,4 +103,4 @@ To only prepare the networks, you can run the scripts up to the point before opt
.. code:: bash
projects/pypsa-eur-sec % snakemake prepare_sector_networks
projects/pypsa-eur-sec % snakemake -j1 prepare_sector_networks

33
doc/myopic.rst
View File

@ -4,26 +4,24 @@
Myopic transition path
##########################################
The myopic code can be used to investigate progressive changes in a network, for instance, those taking place throughout a transition path. The capacities installed in a certain time step are maintained in the network until their operational lifetime expires.
The myopic code can be used to investigate progressive changes in a network, for instance, those taking place throughout a transition path. The capacities installed in a certain time step are maintained in the network until their operational lifetime expires.
The myopic approach was initially developed and used in the paper `Early decarbonisation of the European Energy system pays off (2020) <https://arxiv.org/abs/2004.11009>`__ but the current implementation complies with the pypsa-eur-sec standard working flow and is compatible with using the higher resolution electricity transmission model `PyPSA-Eur <https://github.com/PyPSA/pypsa-eur>`__ rather than a one-node-per-country model.
The current code applies the myopic approach to generators, storage technologies and links in the power sector and the space and water heating sector.
The current code applies the myopic approach to generators, storage technologies and links in the power sector and the space and water heating sector.
The transport sector and industry are not affected by the myopic code. In essence, the electrification of road and rail transport, the percentage of electric vehicles that allow demand-side management and vehicle-to-grid services, and the transformation in the different industrial subsectors do not evolve with time. They are kept fixed at the values specified in the configuration file. Including the transport sector and industry in the myopic code is planned for the near future.
The transport sector and industry are not affected by the myopic code. In essence, the electrification of road and rail transport, the percentage of electric vehicles that allow demand-side management and vehicle-to-grid services, and the transformation in the different industrial subsectors do not evolve with time. They are kept fixed at the values specified in the configuration file. Including the transport sector and industry in the myopic code is planned for the near future.
Configuration
=================
PyPSA-Eur-Sec has several configuration options which are collected in a config.yaml file located in the root directory. Users should copy the provided default configuration (`config.default.yaml <https://github.com/martavp/pypsa-eur-sec/blob/master/config.default.yaml>`__) and amend their own modifications and assumptions in the user-specific configuration file (config.yaml).
PyPSA-Eur-Sec has several configuration options which are collected in a config.yaml file located in the root directory. For myopic optimization, users should copy the provided myopic configuration ``config.myopic.yaml`` and make their own modifications and assumptions in the user-specific configuration file (``config.yaml``).
The following options included in the config.yaml file are relevant for the myopic code.
To activate the myopic option select
foresight: 'myopic'
To activate the myopic option select ``foresight: 'myopic'`` in ``config.yaml``.
@ -38,7 +36,7 @@ grouping_years: [1980, 1985, 1990, 1995, 2000, 2005, 2010, 2015, 2019]
**threshold capacity**
if for a technology, node, and grouping bin, the capacity is lower than threshold_capacity, it is ignored
if for a technology, node, and grouping bin, the capacity is lower than threshold_capacity, it is ignored
threshold_capacity: 10
@ -64,7 +62,7 @@ The {planning_horizons} wildcard indicates the timesteps in which the network is
**{co2_budget_name} wildcard**
The {co2_budget_name} wildcard indicates the name of the co2 budget.
The {co2_budget_name} wildcard indicates the name of the co2 budget.
A csv file is used as input including the planning_horizons as index, the name of co2_budget as column name, and the maximum co2 emissions (relative to 1990) as values.
@ -76,43 +74,42 @@ General myopic code structure
The myopic code solves the network for the time steps included in planning_horizons in a recursive loop, so that:
1.The existing capacities (those installed before the base year are added as fixed capacities with p_nom=value, p_nom_extendable=False). E.g. for baseyear=2020, capacities installed before 2020 are added. In addition, the network comprises additional generator, storage, and link capacities with p_nom_extendable=True. The non-solved network is saved in ‘results/run_name/networks/prenetworks_bronwfield’.
1.The existing capacities (those installed before the base year are added as fixed capacities with p_nom=value, p_nom_extendable=False). E.g. for baseyear=2020, capacities installed before 2020 are added. In addition, the network comprises additional generator, storage, and link capacities with p_nom_extendable=True. The non-solved network is saved in ``results/run_name/networks/prenetworks-brownfield``.
The base year is the first element in planning_horizons. Step 1 is implemented with the rule add_baseyear for the base year and with the rule add_brownfield for the remaining planning_horizons.
2.The 2020 network is optimized. The solved network is saved in ‘results/run_name/networks/postnetworks’
3.For the next planning horizon, e.g. 2030, the capacities from a previous time step are added if they are still in operation (i.e., if they fulfil planning horizon <= commissioned year + lifetime). In addition, the network comprises additional generator, storage, and link capacities with p_nom_extendable=True. The non-solved network is saved in ‘results/run_name/networks/prenetworks_bronwfield’.
3.For the next planning horizon, e.g. 2030, the capacities from a previous time step are added if they are still in operation (i.e., if they fulfil planning horizon <= commissioned year + lifetime). In addition, the network comprises additional generator, storage, and link capacities with p_nom_extendable=True. The non-solved network is saved in ``results/run_name/networks/prenetworks-brownfield``.
Steps 2 and 3 are solved recursively for all the planning_horizons included in the configuration file.
rule add_existing baseyear
=======================
==========================
The rule add_existing_baseyear loads the network in ‘results/run_name/networks/prenetworks’ and performs the following operations:
1.Add the conventional, wind and solar power generators that were installed before the base year.
2.Add the heating capacities that were installed before the base year.
2.Add the heating capacities that were installed before the base year.
The existing conventional generators are retrieved from the `powerplants.csv file <https://pypsa-eur.readthedocs.io/en/latest/preparation/build_powerplants.html?highlight=powerplants>`__ generated by pypsa-eur which, in turn, is based on the `powerplantmatching <https://github.com/FRESNA/powerplantmatching>`__ database.
Existing wind and solar capacities are retrieved from `IRENA annual statistics <https://www.irena.org/Statistics/Download-Data>`__ and distributed among the nodes in a country proportional to capacity factor. (This will be updated to include capacity distributions closer to reality.)
Existing heating capacities are retrieved from the report `Mapping and analyses of the current and future (2020 - 2030) heating/cooling fuel deployment (fossil/renewables)
Existing heating capacities are retrieved from the report `Mapping and analyses of the current and future (2020 - 2030) heating/cooling fuel deployment (fossil/renewables)
<https://ec.europa.eu/energy/studies/mapping-and-analyses-current-and-future-2020-2030-heatingcooling-fuel-deployment_en?redir=1>`__
The heating capacities are assumed to have a lifetime indicated by the parameter lifetime in the configuration file, e.g 25 years. They are assumed to be decommissioned linearly starting on the base year, e.g., from 2020 to 2045.
Then, the resulting network is saved in ‘results/run_name/networks/prenetworks_brownfield’
Then, the resulting network is saved in ``results/run_name/networks/prenetworks-brownfield``.
rule add_brownfield
================
===================
The rule add_brownfield loads the network in ‘results/run_name/networks/prenetworks’ and performs the following operation:
1.Read the capacities optimized in the previous time step and add them to the network if they are still in operation (i.e., if they fulfil planning horizon < commissioned year + lifetime)
Then, the resulting network is saved in ‘results/run_name/networks/prenetworks_brownfield.’
Then, the resulting network is saved in ``results/run_name/networks/prenetworks_brownfield``.

9
doc/overnight.rst Normal file
View File

@ -0,0 +1,9 @@
.. _overnight:
##########################################
Overnight (greenfield) scenarios
##########################################
The default is to calculate a rebuilding of the energy system to meet demand, a so-called overnight or greenfield approach.
For this, use ``foresight : 'overnight'`` in ``config.yaml``, like the example in ``config.default.yaml``.