Implement workaround for oemof.solph 0.5.1 compatibility #134
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a period=0 to lines where the time index is called, which has been changed to a tuple of (period, time step) in oemof.solph 0.5.1
4 tasks
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Version 0.5.1 of oemof.solph introduced the (experimental) feature of supporting multi-period investments:
https://oemof-solph.readthedocs.io/en/stable/changelog.html#v0-5-1-august-31st-2023
The update changes the way certain objects with a time index are referenced, since the index now consists of a (periods, timesteps) tuple. This breaks the DHNx code in a couple of places.
Add a period=0 to lines where the time index is called, in a try-except statement that retains compatibility with oemof.solph 0.5.0
Fixes #133.