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

minor fixes

Browse Source
This commit is contained in:
Fabian Neumann 2022-11-27 18:38:32 +01:00
parent 5ee9e976b8
commit 88db7a458f
3 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
.DS_Store vendored
View File

Binary file not shown.

10
doc/myopic.rst
View File

@ -85,7 +85,8 @@ E.g. ``'cb40ex0'`` splits a carbon budget equal to 40 GtCO_2 following an expone
They can also follow some user-specified path, if defined `here <https://github.com/PyPSA/pypsa-eur-sec/blob/413254e241fb37f55b41caba7264644805ad8e97/config.default.yaml#L56>`_.
The paper `Speed of technological transformations required in Europe to achieve different climate goals (2022) <https://doi.org/10.1016/j.joule.2022.04.016>`__ defines CO_2 budgets corresponding to global temperature increases (1.5C – 2C) as response to the emissions. Here, global carbon budgets are converted to European budgets assuming equal-per capita distribution which translates into a 6.43% share for Europe. The carbon budgets are in this paper distributed throughout the transition paths assuming an exponential decay. Emissions e(t) in every year t are limited by
$e(t) = e_0 (1+ (r+m)t) e^(-mt)$
.. math::
e(t) = e_0 (1+ (r+m)t) e^(-mt)
where r is the initial linear growth rate, which here is assumed to be r=0, and the decay parameter m is determined by imposing the integral of the path to be equal to the budget for Europe. Following this approach, the CO_2 budget is defined. Following the same approach as in this paper, add the following to the ``scenario.sector_opts``
E.g. ``-cb25.7ex0`` (1.5C increase)
@ -98,13 +99,12 @@ 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-brownfield``.
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``
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-brownfield``.
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 ``config.yaml``.

12
doc/supply_demand.rst
View File

@ -44,11 +44,11 @@ Annual heat demands per country are retrieved from `JRC-IDEES <https://op.europ
*Space heating*
The space heating demand can be exogenously reduced by retrofitting measures that improve the buildings’ thermal envelopes [Refer to PyPSA-Eur-Sec config file, `line 212 <https://github.com/PyPSA/pypsa-eur-sec/blob/3daff49c9999ba7ca7534df4e587e1d516044fc3/config.default.yaml#L212>`_.
The space heating demand can be exogenously reduced by retrofitting measures that improve the buildings’ thermal envelopes.
.. literalinclude:: ../config.default.yaml
:language: yaml
:lines: 212
:lines: 205
Co-optimsing of building renovation is also possible, if it is activated in the `config file <https://github.com/PyPSA/pypsa-eur-sec/blob/3daff49c9999ba7ca7534df4e587e1d516044fc3/config.default.yaml#L222>`_.
Renovation of the thermal envelope reduces the space heating demand and is optimised at each node for every heat bus. Renovation measures through additional insulation material and replacement of energy inefficient windows are considered.
@ -394,19 +394,19 @@ Two alternative routes are used today to manufacture steel in Europe. The primar
The primary route uses blast furnaces in which coke is used to reduce iron ore into molten iron, which is then converted into steel:
.. math::
CO_2 + C \xrightarrow{} 2 CO
CO_2 + C \xrightarrow{} 2 CO
.. math::
3 Fe_2O_3 + CO \xrightarrow{} 2 Fe_3O_4 + CO
3 Fe_2O_3 + CO \xrightarrow{} 2 Fe_3O_4 + CO
.. math::
Fe_3O_4 + CO \xrightarrow{} 3 FeO + CO_2
Fe_3O_4 + CO \xrightarrow{} 3 FeO + CO_2
.. math::
FeO + CO \xrightarrow{} Fe + CO_2
FeO + CO \xrightarrow{} Fe + CO_2
The primary route of steelmaking implies large process emissions of 0.22 t :math:`_{CO_2}` /t of steel, amounting to 7% of global greenhouse gas emissions `(Vogl et. al) <https://doi.org/10.1016/j.joule.2021.09.007>`_.