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
For generation/storage resources, if Max_Cap_MW <= 0 then capacity investments are treated as unconstrained, e.g. in investment_discharge.jl we have:
@constraint(EP, cMaxCap[y in intersect(dfGen[dfGen.Max_Cap_MW.>0, :R_ID], 1:G)], eTotalCap[y] <= dfGen[y, :Max_Cap_MW])
Currently, there is no parallel option for inter-zonal transmission capacity investments. They are always constrained as in load_network_data.jl we have the following code:
if setup["NetworkExpansion"]==1
# Read between zone network reinforcement costs per peak MW of capacity added
inputs_nw["pC_Line_Reinforcement"] = to_floats(:Line_Reinforcement_Cost_per_MWyr) / scale_factor # convert to million $/GW/yr with objective function in millions
# Maximum reinforcement allowed in MW
**#NOTE: values <=0 indicate no expansion possible**
**inputs_nw["pMax_Line_Reinforcement"] = map(x->max(0, x), to_floats(:Line_Max_Reinforcement_MW)) / scale_factor # convert to GW**
inputs_nw["pTrans_Max_Possible"] += inputs_nw["pMax_Line_Reinforcement"]
end
We should modify this so that values for pMax_Line_Reinforcement <=0 instead treats expansion along that line as unconstrained.
The text was updated successfully, but these errors were encountered:
For generation/storage resources, if
Max_Cap_MW <= 0
then capacity investments are treated as unconstrained, e.g. ininvestment_discharge.jl
we have:@constraint(EP, cMaxCap[y in intersect(dfGen[dfGen.Max_Cap_MW.>0, :R_ID], 1:G)], eTotalCap[y] <= dfGen[y, :Max_Cap_MW])
Currently, there is no parallel option for inter-zonal transmission capacity investments. They are always constrained as in
load_network_data.jl
we have the following code:We should modify this so that values for
pMax_Line_Reinforcement <=0
instead treats expansion along that line as unconstrained.The text was updated successfully, but these errors were encountered: