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
if p.s.site.mg_tech_sizes_equal_grid_sizes
@constraint(m, [t in p.techs.elec],
m[:dvMGsize][t] == m[:dvSize][t]
)
While the constraint above does get correctly applied, the value for binMGTechUsed is 0 in this case. And the result Outage.pv_microgrid_size_kw = dvMGsize * binMGTechUsed, which is why this results is 0.
It looks like PV is never(??) run simultaneous to a generator?! And, if the generator needs to be used at all in a given modeled outage, then it will be used to cover all of the critical load, if possible.
In this example, I set the max generator size to something lower than the critical load. REopt chose to add a battery (expected) and in no cases is PV serving the critical load along with the generator (unexpected): https://reopt.nrel.gov/tool/results/54f422c9-d411-41e1-99c9-81020887fd12
DISCOVERY: PV DOES get used in the outage when the same model is run with Xpress vs. HiGHS. See inputs for this scenario in comments
Potential bug, but also confusing as to why different results are obtained with Xpress: It looks like solver_is_compatible_with_indicator_constraints is false with Xpress, but is expected to be true --> made a separate issue for this: p.s.settings.solver_name not getting updated #458
The text was updated successfully, but these errors were encountered:
Turns out this is because the fuel cost was insignificant enough to the objective function that the model can find a solution within the tolerance before finding the lower fuel cost solution that uses PV instead of the generator during outages.
binMGTechUsed
is 0 in this case. And the resultOutage.pv_microgrid_size_kw
=dvMGsize
*binMGTechUsed
, which is why this results is 0.Outages.pv_microgrid_size_kw
equal to the PV size: https://reopt.nrel.gov/tool/results/94d0197b-2f1a-4b3b-885c-814ecafc29cefalse
with Xpress, but is expected to betrue
--> made a separate issue for this: p.s.settings.solver_name not getting updated #458The text was updated successfully, but these errors were encountered: