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

Wording in flow_cap_min #653

Closed
sstroemer opened this issue Aug 7, 2024 · 1 comment · Fixed by #672
Closed

Wording in flow_cap_min #653

sstroemer opened this issue Aug 7, 2024 · 1 comment · Fixed by #672

Comments

@sstroemer
Copy link
Contributor

sstroemer commented Aug 7, 2024

Description

Currently, flow_cap_min states

Limits flow_cap to a minimum. NOTE: this will force flow_cap to a minimum value unless cap_method is set to integer. If cap_method=integer, this will be scaled by the number of integer units of a technology purchased.

which might be misinterpreted by some users (c.f. the comment posted by @brynpickering in #643).

Related links

Version

latest (48148b8)

Proposed change

This acts as lower limit (lower bound) for flow_cap. If cap_method=integer, this will be scaled by the number of integer units of a technology purchased.

Note:

If cap_method = continuous (which is set by default), then setting flow_cap_min to any value greater than 0 forces the model to always respect that limit, preventing it from not investing into the technology. Use this to enforce given investment plans, or to account for existing technologies that cannot be decommissioned.

An example: If cap_method = continuous and flow_cap_min = 100, then flow_cap has to be at least 100. It going to 0 is not possible, unless you switch to cap_method = integer (see cap_method).

@brynpickering
Copy link
Member

Proposed change sounds good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants