Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

purchased binary variable isn't linked to energy_cap if energy_cap_max/_min/_equals isn't defined #565

Open
2 of 3 tasks
brynpickering opened this issue Feb 12, 2024 · 0 comments
Labels
bug has-workaround The issue describes a valid workaround until the primary issue is solved v0.6 Version 0.6

Comments

@brynpickering
Copy link
Member

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

@brynpickering brynpickering added bug has-workaround The issue describes a valid workaround until the primary issue is solved v0.6 Version 0.6 labels Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug has-workaround The issue describes a valid workaround until the primary issue is solved v0.6 Version 0.6
Projects
None yet
Development

No branches or pull requests

1 participant