`purchased` binary variable isn't linked to `energy_cap` if `energy_cap_max`/`_min`/`_equals` isn't defined
brynpickering opened this issue · comments
What happened?
If the purchase cost is defined but some limit on energy_cap isn't defined, then there is no constraint to link purchase with energy_cap. This means that you get zeroes across the board for purchase even when technologies that are using this binary decision variable have a non-zero energy_cap.
The straightforward workaround is to set energy_cap_max to some value that is akin to bigM: large enough not to impact model results but small enough not to cause numerical trouble.
Which operating systems have you used?
- macOS
- Windows
- Linux
Version
v0.6.10
Relevant log output
No response