You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked that this issue has not already been reported.
Bug summary
When a grid with non-variable generators with Pmax = 0 is used to prepare inputs for SwitchWrapper, the corresponding expansion candidate generators have gen_full_load_heat_rate = 0.
You're right, this issue was not caught in either the review for this function (#35) or in any subsequent testing. If I'm reading that exploratory code correctly, it's neither adding a meaningful heat rate nor constraining the build decisions to zero, but adding an arbitrarily high heat rate such that this generator would not be chosen to be built except in extreme circumstances.
You're right, this issue was not caught in either the review for this function (#35) or in any subsequent testing. If I'm reading that exploratory code correctly, it's neither adding a meaningful heat rate nor constraining the build decisions to zero, but adding an arbitrarily high heat rate such that this generator would not be chosen to be built except in extreme circumstances.
Yep that's right, it is quick and dirty in research exploration. Just put the link here so that we know it is not "hided" somewhere:), but no need to follow that 999 temp logic. It is certainly better to make it more robust in the design phase.
🪲
Bug summary
When a grid with non-variable generators with
Pmax = 0
is used to prepare inputs for SwitchWrapper, the corresponding expansion candidate generators havegen_full_load_heat_rate = 0
.Code for reproduction
Actual outcome
Code runs, but
gen_full_load_heat_rate
is0
for the ten natural gas generators with Pmax = 0.Expected outcome
Meaningful heat rates for these generators or in absence of that,
gen_capacity_limit_mw
= 0.Environment
Please specify your platform and versions of the relevant libraries you are using:
git rev-parse origin/HEAD
): 6f18adeAdditional context
The problem seems to come from the
linearize_gencost
function:The only entries in
single_segment_slope
that are zero, but correspond to a generatThe text was updated successfully, but these errors were encountered: