source_max/sink_max etc. parameters to source_use_max/sink_use_max etc.
units and purchased merged into purchased_units. Setting purchased_units_max to 1 creates the same result as the former purchased binary variable.
Moved some milp constraints to base from one of the example custom math YAMLs (available_flow_cap). This allows a user to define eitherflow_cap_per_unit or flow_cap_max for a technology with integer capacity units. This way the time-varying integer variable operating_units can be applied to the case where purchased_units is being used as a binary variable and flow_cap remains continuous, where it used to only apply with flow_cap being fixed to a multiple of purchased_units.
Fixes #451
Summary of changes in this pull request:
source_max
/sink_max
etc. parameters tosource_use_max
/sink_use_max
etc.units
andpurchased
merged intopurchased_units
. Settingpurchased_units_max
to 1 creates the same result as the formerpurchased
binary variable.base
from one of the example custom math YAMLs (available_flow_cap
). This allows a user to define eitherflow_cap_per_unit
orflow_cap_max
for a technology with integer capacity units. This way the time-varying integer variableoperating_units
can be applied to the case wherepurchased_units
is being used as a binary variable andflow_cap
remains continuous, where it used to only apply withflow_cap
being fixed to a multiple ofpurchased_units
.Reviewer checklist: