Merged
Conversation
…and_transport_electric_share
…into improve-transport-sector
Collaborator
Author
|
#95 will partially supersede / refine this PR |
6 tasks
Collaborator
Author
|
I added more verbose printing to the modify_prenetwork. This is for 2025: In the screenshots above I divided the BEV charger capacity by an incorrect factor, this one should be correct (and it's the same number when multiplied with said factor) |
toniseibold
approved these changes
Jul 18, 2025
Contributor
toniseibold
left a comment
There was a problem hiding this comment.
Just curious if we could delete the transport_ratios from the config.
Maybe a bit confusing first setting them and then overwriting them in the workflow.
Collaborator
Author
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem:
In modify_prenetwork the mobility demand is rescaled towards the data from Aladin. However, the number of cars is still taken from the pypsa-eur workflow. As a consequence:
BEV chargercapacity is not aligned with theland transport EVload (e.g. in 2025 ~30 TWh demand from 3.1 million EVs, whereas pypsa-eur has ~25 TWh demand from 7 milllion EVs - both is not aligned with latest consumption data from DE)land_transport_electric_sharebehaves very unintuitively.This PR:
land_transport_electric_sharedoes not matter anymore. A warning has been added and the config values of e.g.land_transport_electric_sharein pypsa.de.yaml have been set to dummy values. (They need to remain >0 or else the loads won't be created.)iiasa_database:ageb_for_transport(true by default). If this value istruethan the 2020 and 2025 transport demand will be read/extrapolated from the 2020/2024 AG Energiebilanzen publication for Germany. In this case the number of vehicles will be taken from the corresponding publication of the Kraftfahrtbundesamt (for 1. January 2021/2026(extrapolated))Before this PR:
After this PR:
Update
I added a feature to switch the 2020 and 2025 to AGEB and Kraftfahrtbundesamt (for number of vehicles)
In a similar way we could insert the 2030 data from e.g. UBA Projektionsbericht
Addtional observation not adressed here
The number of cars dimensions the BEV charger
The number of cars is the number of passenger cars, i.e. LDV-BEV (and PHEV)
however the BEV load includes both LDV and HDV
Thus the BEV charger may be underdimensioned
Before asking for a review for this PR make sure to complete the following checklist:
ariadne_allcompletes without errorsexport_ariadne_variableshas been adapted to the changesChangelog.mdmainhas been merged into the PRYYYYMMDDdescriptive_title