-
Notifications
You must be signed in to change notification settings - Fork 134
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
OffsetTransformer with nonconvex and investment options #861
Comments
There was a reason putting the offset on the inflow, but I don't remember exactly. It may be that this matters only in the case, if Nonetheless, there should be nothing against opening a PR. It would be really nice in combination with an investment. It makes for sure sense, if you take the new structure of the flows as basis. If it was really just the case I described above, you could then also issue a warning. Or you make it more general somehow, that you can set the offset arbitrarily to the in- or outflow, that would be cool anyway. |
I believe it would make more sense to define the |
Seeing that the PR went through and that the last interaction was a year ago, I take the liberty to close this issue. Stumbled upon it while researching for #1010 |
Currently, the
OffsetTransformer
can be used ONLY when itsnominal_value
is already known, which means, it is not possible to find the optimal capacity of a transformer with a given efficiency curve (instead of a single efficiency).Nevertheless, after #856 is finalized, it will be possible to have this functionality. But the
OffsetTransformer
needs to be adjusted because, in the current version, thenonconvex
option MUST be defined for the input flow. This will cause problems if the optimal capacity of the component is unknown. In this situation, thenonconvex
option and theinvestment
option must be defined for the output flow. The reason is that theep_cost
in the investment option should apply to the outflow of assets, and it is impossible to map this value for the input flow. Moreover, we cannot defineinvestment
in the outflow andnonconvex
in the inflow because, in this case, since thenominal_value
would be unknown, both these options must be used in the same flow.I am making some changes in the
OffsetTransformer
and will soon open a pull request about the proposed changes, but it would be nice to discuss it here, if there is disagreement on this issue.The text was updated successfully, but these errors were encountered: