PyPSA / pypsa-ariadne

High resolution, sector-coupled model of the German Energy System
https://ariadneprojekt.de/en/model-documentation-pypsa/
MIT License
6 stars 4 forks source link

Review suggestions for `feature_jg` #8

Closed fneum closed 5 months ago

fneum commented 5 months ago

review for https://github.com/PyPSA/pypsa-ariadne/pull/6

@JulianGeis looks very good! I have revised the code to:

My questions:

  1. The build year of the hydrogen pipelines is not considered, right? In prepare_sector_network, one could add a line
custom_pipes.query("build_year <= @investment_year", inplace=True)

after reading the file so that the minimum capacities and routes depend on the planning horizon.

  1. Is the clipping to a minimum pressure of 30 bar and a minimum build year 2030 necessary? Should the latter maybe be a config option?

  2. Does it make a difference if you set the acceptable length ratio to a higher value?

  3. Did it make a difference if you applied the line segmentation approach?

JulianGeis commented 5 months ago

Answering your questions:

  1. Right, the build year is not yet considered. I also did not put too much effort in extracting it properly. However with your suggested method it is done properly. If one implements the selection by date as you suggest, the clipping should not be done. Actually, I did not really do a clipping for the year as the clipping year was set to 2020. I just wanted to exclude unrealistic values.

  2. Clipping the minimum pressure to 30 bar is not really necessary. There are only 9 values below 30 anyways, which are all 25. Clipping the build year is also not necessary.

  3. The current value of 2 excludes these 8 pipes: image Most of them seem ok, if you look at the names of the start and end, but the length is really of. It would not change the network massively if they were included. However, I thought it would be more conservative to not include them. But especially the line in Bavaria is making sense and is an important one. So I would be okay with just keeping them.

  4. The line segmentation approach did lead to different results in terms of pipelines. For the 22 clusters these were the two results:

Without line segmentation: image

With line segmentation: image

This makes sense, as the segmentation creates more start / end points which may lie within a region that was not included before as the pipe went directly trough. This is for example the case for CZ. It can also happen that some pipes or connections are no more present as it is the case for Germany. This happens if the segmentation splits pipes, so that they connect A and B via C and not directly again. The capacity is still there only going trough another location.

fneum commented 5 months ago

All good!

For 3., I would also be ok with keeping them.

For 4., I'm in favour of apply the line segmentation by default.