-
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
base: master
Are you sure you want to change the base?
Conversation
…chnology-data into nrel_atb_usa_costs
…ransition/technology-data into nrel_atb_usa_costs
…ransition/technology-data into nrel_atb_usa_costs
…ransition/technology-data into nrel_atb_usa_costs
Thanks @finozzifa for the detailed description. I would just add something about |
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
tax_credit_case
equalsITC, None, PTC + ITC, PTC
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
Other noteworthy changes
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.