forked from PyPSA/technology-data
-
Notifications
You must be signed in to change notification settings - Fork 0
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
add NREL/ATB electricity costs for the US #1
Open
finozzifa
wants to merge
105
commits into
master
Choose a base branch
from
nrel_atb_usa_costs
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
…chnology-data into nrel_atb_usa_costs
…ransition/technology-data into nrel_atb_usa_costs
…ransition/technology-data into nrel_atb_usa_costs
* Add PTES technology with correct parameters, reassign TTES parameters * Add PTES, reassign TTES param * Add energy to power ratio calculation for ltes * Add energy to power ratio calculation for ltes * Update release notes * improve readability * updating charging efficiency LTES * Update decentral water storage to DEA data and include energy to power ratio * minor changes to enhance readability * minor changes to enhance readability * small changes - ready for PR
…sts. Plus rename file
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.
Goals
This pull request contains the changes performed by @danielelerede-oet and myself (@finozzifa) as agreed with @martacki and Johannes (could not find his github alias).
Proposed final goal: this pull request is the first (intermediate) step of a set of changes that aim at granting the possibility to the model users to use country-specific cost assumptions.
Goal of this pull request: This work in particular proposes an intermediate step and creates a sub-folder outputs/US, where the outputs/costs_yyyy.csv files are copied and updated with NREL/ATB data.
Input and output schemas
NREL/ATB input values and schema
The NREL/ATB electricity data source is available here.
We require the cost assumptions for the years 2020, 2025, 2030, 2035, 2040, 2045 and 2050. The cost assumptions for 2020 are obtained from atb_e_2022 dataset, whereas those for the other years from the atb_e_2024 dataset. The schema of these files is unfortunately slightly different. Namely:
Schema of atb_e_2022
Schema of atb_e_2024
We consider a subset of such columns. This can be configured with the configuration from the
config.yaml
fromconfig["nrel_atb"]["nrel_atb_columns_to_keep"]
. For this pull request, the columns taken arewhere in particular
atb_year
equals the year in the file name. For exampleatb_year = 2022
for atb_e_2022 oratb_year = 2024
for atb_e_2024core_metric_variable
equals the year for which the cost assumption is madecore_metric_parameter
has various values. We considerscenario
equalsModerate, Conservative, Advanced
outputs/US/costs_yyyy.csv values and schema
Changes
Changes in the workflow
The workflow has been updated as follows:
rule compile_cost_assumptions
generatesoutputs/costs_yyyy.csv
filesrule compile_cost_assumptions_nrel
takes theoutputs/costs_yyyy.csv
files, reads-in the nrel/atb inputs, processes them and outputs a dedicated set of costs for the US inoutputs/US/costs_yyyy.csv
The "high level" description of what compile_cost_assumptions_nrel.py does
The "high level" description of what the script does is:
outputs/cost_yyyy.csv
fileretrofits
technologies) or CAPEX (for any other technology) and changes its unit from$/KW-yr
to%-yr
nuclear
andbiomass
.Oil
andgas
US-specific fuel costs are fetched from the World Bank's annual prices with projections up to 2030 (based on World Bank's 2026 estimations).Coal
fuel cost is fetched from the EIA Annual Coal Report 2023.Other noteworthy changes
Aligning the technology names of atb_e_2022 to the names of atb_e_2024
The technologies listed below have different name between atb_e_2022.parquet and atb_e_2024.parquet. Therefore the technologies on the left-hand side are renamed to the names on the right-hand side.
Discarded technologies
The following technologies are present in the input file atb_e_2022.parquet. They are however not present in atb_e_2024.parquet. They are therefore discarded from the final cost output files. They are:
environment.yaml
We choose to take the the input datasets atb_e_2022 and atb_e_2024 in parquet format. This is because the corresponding csv files have a size which is significantly larger. This choice brings about the following addition to the environment.yaml file
unit tests
We added a
test
folder to include unit tests for the functions included inscripts/compile_cost_assumptions_nrel.py
inputs/manual_input.csv
New technologies have been added to
manual_inputs.csv
.Checklist
doc
.environment.yaml
(if applicable).doc/release_notes.rst
of the upcoming release is included.