-
Notifications
You must be signed in to change notification settings - Fork 198
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 coal and gas CC technologies #1200
base: main
Are you sure you want to change the base?
Changes from all commits
9bbda88
ea689a8
8521eb7
087624d
f13e036
debd0c5
d5e84fb
08bf56f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -358,6 +358,7 @@ costs: | |
year: 2030 | ||
version: v0.6.2 | ||
discountrate: [0.071] #, 0.086, 0.111] | ||
scenario: "Moderate" # "Advanced", "Moderate", or "Conservative" | ||
# [EUR/USD] ECB: https://www.ecb.europa.eu/stats/exchange/eurofxref/html/eurofxref-graph-usd.en.html # noqa: E501 | ||
USD2013_to_EUR2013: 0.7532 # [EUR/USD] ECB: https://www.ecb.europa.eu/stats/exchange/eurofxref/html/eurofxref-graph-usd.en.html | ||
rooftop_share: 0.14 # based on the potentials, assuming (0.1 kW/m2 and 10 m2/person) | ||
|
@@ -508,6 +509,9 @@ sector: | |
network: false # ALWAYS FALSE for now (NOT USED) | ||
network_data: GGIT # Global dataset -> 'GGIT' , European dataset -> 'IGGIELGN' | ||
network_data_GGIT_status: ["Construction", "Operating", "Idle", "Shelved", "Mothballed", "Proposed"] | ||
gas_NGCC: false # if true, Natural Gas 2-on-1 Combined Cycle (F-Frame) plant is added | ||
CC: false # enable gas carbon capture technologies | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My feeling is that it would be great to keep harmonise using upper and lowercase across the code: we have lower-cased There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually, my thought was to change everywhere to uppercase There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Totally agree 🙂 |
||
gas_CC_techs: ["NG 2-on-1 Combined Cycle (F-Frame) 95% CCS", "NG 2-on-1 Combined Cycle (F-Frame) 97% CCS"] # Natural Gas 2-on-1 Combined Cycle (F-Frame) plants with 95% and 97% capture rate | ||
hydrogen: | ||
network: true | ||
H2_retrofit_capacity_per_CH4: 0.6 | ||
|
@@ -522,6 +526,9 @@ sector: | |
coal: | ||
spatial_coal: true | ||
shift_to_elec: true # If true, residential and services demand of coal is shifted to electricity. If false, the final energy demand of coal is disregarded | ||
coal_IGCC: false # If true, coal integrated gas combined-cycle (IGCC) plants are added | ||
CC: false # enable coal carbon capture technologies | ||
coal_CC_techs: ["Coal-95%-CCS", "Coal-99%-CCS", "Coal-IGCC-90%-CCS"] # coal plant with 95% capture rate, coal plant with 99% capture rate, coal integrated gas combined-cycle plant with 90% capture rate | ||
lignite: | ||
spatial_lignite: false | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be great to add a comment on what exactly is meant by
scenario
here, as we have quite many of them in the config 😄 Probably, adjustment of the naming can help, as well: liketech_scenario
orcosts_scenario
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review @ekatef. I will probably remove these changes. As it needs to be applied with @danielelerede-oet and @finozzifa PR on cost assumption integration. Being under costs section scenario is plan to mean
cost scenario
. But if it can lead to misunderstanding then I agree we can name it ascost_scenario
.