Closes #74.

Changes proposed in this Pull Request

This PR integrates the PEMMDB hydro inflow data for the 2024 TYNDP into the workflow introducing a data pipeline to deal with the raw data and build hydro profiles that can be used for different hydro technologies.

Available hydro technologies are:

• PS Closed
• PS Open
• Pondage
• Reservoir
• Run of River

For more information and the differentiation between the different technologies, please refer to ENTSO-E's 'Hydropower modelling methodology' (2019)

Note: Similar to #71, this PR serves to facilitate a sub-workflow for creation of the hydro inflow profiles but does not yet attach them to any technologies yet. This will be added in a follow up PR.

Additionally required steps are:

• Inclusion of TYNDP hydro technologies using PEMMDB hydro inflows
• Adding existing capacities for TYNDP hydro technologies from PEMMDB data ([PARENT] Inclusion of existing infrastructure from PEMMDB & investment candidates #64)

The supplied available inflow profiles were reviewed for consistency with available PEMMDB capacities in #96.
The review showed that no necessary data is missing entirely while there are some inflow profiles with zero-values which warrant further clarification whether this is indeed correct. The issue is reported in the Open-TYNDP transparency report.

Tasks

• Introduce data pipeline for cleaning hydro inflow data
• Add retrieve rule for Hydro Inflows data
• Merge master
• Build hydro profiles
• Update the documentation of the PR
• Add release note
• fix CI
• Improve documentation of retrieve_tyndp_hydro_inflows rule
• Validate data per year and against available capacities (see feat: share testing notebook for hydro inflow data #96)

Workflow

The introduced workflow data pipeline for the PEMMDB hydro inflow data includes the following steps:

• (new) retrieve_tyndp_hydro_inflows: Rule to retrieve the TYNDP 2024 hydro inflow data and save in the tyndp_2024_bundle directory
• (new) clean_tyndp_hydro_inflows: Rule to clean the TYNDP hydro inflows. This rule depends on two wildcards:
  • The planning_horizon wildcard which can be one of the years (2030, 2040 and 2050) for which hydro inflow data is available.
  • The tech wildcard which specifies the hydroelectric technology ("Run of River", "Pondage", "Reservoir", "PS Open", "PS Closed") for which the inflow profile needs to be extracted. This allow parallelization of the processing of the different technologies.
• (new) build_tyndp_hydro_profile

  • The rule provides a resources/profile_hydro_tyndp.nc file with the following structure:

    Field	Dimensions	Description
    inflow	bus, time, year, hydro_tech	Inflow to the state of charge (in MW), e.g. due to river inflow in hydro reservoir.

The following graph illustrates the workflow from the cleaning step to prepare_sector_network for config/test/config.tyndp.yaml:

Open issues

The review (#96) showed that no necessary data is missing entirely while there are some inflow profiles with zero-values which warrant further clarification whether this is indeed correct.

The following hydro inflow profiles show zero-values while having specified turbine capacities:

2030

Run of River

• ITS1

Reservoir

• SI00

PS Open

• NON1
• FR00

2040

Run of River

• ITS1

Reservoir

• SI00

PS Open

• NON1
• FR00
• MK00

2050

Run of River

• ITS1

Reservoir

• SI00

PS Open

• NON1
• FR00
• MK00

Notes

Checklist

• I tested my contribution locally and it works as intended.
• Code and workflow changes are sufficiently documented.
• Changed dependencies are added to envs/environment.yaml.
• Changes in configuration options are added in config/config.default.yaml.
• Changes in configuration options are documented in doc/configtables/*.csv.
• Changes in configuration options are added in config/test/*.yaml.
• OET license identifier is added to all edited or newly created code files.
• Sources of newly added data are documented in doc/data_sources.rst.
• A release note doc/release_notes.rst is added.