-
Notifications
You must be signed in to change notification settings - Fork 129
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
Make windoff independent from windon #1782
base: develop
Are you sure you want to change the base?
Conversation
…om mrremind wind values
…offshoreNearterm Need to test with most recent changes
…horeNearterm Trying to pull little changes
modules/40_techpol/NDC/equations.gms
Outdated
sum(teWind(te), vm_cap(t,regi,te,"1")) | ||
=g= p40_TechBound(t,regi,"wind")*0.001 | ||
sum(teWind(te)$(sameas(te,"windon") OR sameas(te,"windoff")), vm_cap(t,regi,te,"1")) | ||
=g= p40_TechBound(t,regi,"windon") * 0.001 |
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.
Actually, I find it potentially confusing if you read in a "all-wind target" as "windon" and then apply it to all wind.
so if you keep "wind" as an empty technology, this makes it very easy for you - just read in the all-wind target for the technology "wind", and then apply it to the sum of both.
so
sum(teWind(te)$(sameas(te,"windon") OR sameas(te,"windoff")), vm_cap(t,regi,te,"1"))
=g= p40_TechBound(t,regi,"wind") * 0.001
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.
Confirmed that bounds are for the sum of windOn and windOff:
mrremind/R/convertREN21.R
x_tmp[, , "Wind"] <- x_tmp[, , "Wind_ON"] + x_tmp[, , "Wind_OFF"]
Let's use pewin
for such bounds, which then offers a choice: either we update mrremind to also output pewin bounds, or we re-separate the windon and windoff bounds (hopefully without to much trouble).
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.
Great work, Fabrice!
I added many small comments, but there is one thing that I expect to potentially change results in an unwanted way - the removal of the rescaling of outputs from net to gross production in 04_PE_FE.
maybe I overlooked something, but currently it seems like you removed that, and I don't understand why.
Hey, thanks a lot for your fast and thorough reviews. |
no, I don't know if the bounds are for wind onshore or wind offshore. maybe using pewin for the read-in of "all wind" targets is a good approach. |
Purpose of this PR
So far, the development of wind offshore is tied to that of wind onshore. But offshore has specific requirements, as seen in the issue https://github.com/remindmodel/development_issues/issues/272.
cm_wind_offshore
that made windoff optional (but activated by default for years)Type of change
(Make sure to delete from the Type-of-change list the items not relevant to your PR)
Checklist:
remind2
where it was needed windon replaces wind in reporting (still compatible with wind) pik-piam/remind2#634forbiddenColumnNames
in readCheckScenarioConfig.R in case the PR leads to deprecated switchesFAIL 0
in the output ofmake test
)CHANGELOG.md
has been updated correctlyFurther information (optional):
/p/tmp/fabricel/offshoreRemind09
compScen-offshoreCascadeEU21-2024-09-20_11.32.20-H12.pdf