-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Eurostat2023 data #936
Closed
Closed
Eurostat2023 data #936
Conversation
This file contains 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
Previously the DH share was being multiplied by the population weighting, reducing the DH share with multiple nodes.
Previously this was handled inside prepare_sector_network.py.
Now the script build_district_heat_share.py does what the old function create_nodes_for_heating() in prepare_sector_networks.py did. There is no need to build nodes lists for each heating sector, since all nodes have district heating now.
This makes the distribution of existing heating to urban/rural, residential/services and spatially more transparent.
Without this formatting, there is an error adding a string to a list.
Co-authored-by: Fabian Hofmann <fab.hof@gmx.de>
The source URL has changed. It represents the year 2012 and is only for buildings, not district heating. So the capacities for urban central are now set to zero from this source.
This is because old costs default (25) is longer than all heating technologies (20). Script was distributing across 25 years, then throwing out boilers older than 20 years, an inconsistent behaviour. Now existing boilers are smoothly distributed across 20 years.
This allows them to cover heat demand peaks e.g. 10% higher than those in the data. The disadvantage of manipulating the costs is that the capacity is then not quite right. This way at least the costs are right. Doing it properly would require introducing artificial peaks, but this creates new problems (e.g. what is going on with wind/solar/other demand).
This is required so that other models can do CO2 limits on each type of aviation separately.
This reverts commit b1ba64a.
This reverts commit 29e0978.
Also allow industrial coal demand to be regional (so we can include them in regional CO2 constraints).
This is so that the full EU28 ammonia demand can be correctly subtracted in the build_industry_sector_ratios.py script. No other downstream scripts are affected by this change.
in build_industry_sector_ratios.py. In the config the units are Mt/a, they are multiplied by MWh/t, but what is desired is GWh/a.
for more information, see https://pre-commit.ci
I.e. split basic chemicals (without ammonia) into MeOH, Cl and HVC. This now agrees with scheme for industrial sectors tomorrow.
This makes sure the distribution key is correct when only subsets of countries are used. This is then consistent with the HVC, MeOH and Cl totals being EU28 totals. Without this change, industry production is overestimated when using subsets of countries. Or the user has to adjust the totals for industrial production themselves.
This uniformises how demand for basic chemicals is calculated. We also avoid unnecessary use of ammonia production separately.
For each country we gradually switch industry processes from today's specific energy carrier usage per ton material output to the best-in-class energy consumption of tomorrow in the industry_sector_ratios.csv. This is done on a per-country basis. The ratio of today to tomorrow's energy consumption is set with the config["industry"]["sector_ratios_fraction_future"] parameter.
cluster nice names as well
…ntry, adjust axis label
Updated files for Switzerland: |
@toniseibold can you merge with the current master instead of And have you done some plausibility checks energy totals before and after the update? |
This was referenced May 12, 2024
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.
Changes proposed in this Pull Request
Reads in the latest eurostat report from 2023 and uses it for building energy totals.
Since the JRC IDEES data is only available for 2015, the energy balances are scaled by the factor of eurostat[report_year]/eurostat[2015] data as well.
The latest swiss energy totals are added to ensure consistent energy totals.
To complement the PR, please add the eurostat data from 2023 to the zenodo data.
Missing is only the passenger car efficiency and the number of passenger cars that are initially in the JRC IDEES but not in the eurostat data set.
Checklist
envs/environment.yaml
.config.default.yaml
.doc/configtables/*.csv
.doc/release_notes.rst
is added.