Introduce variable for storage losses #1090
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think it makes a lot of sense, e.g. for adding custom constraints, to have an explicit variable for the losses of the storage. Note that the formula for the relative lasses is more complicated
vs
but I think the additional variable and constraint is useful and the 1-(1-b)**tau instead of (1-b)**tau changes a value in the lp file, so it will not significantly increase computational time.
PS: I existentially pushed this change to dev, so this PR reverts the revert.