Fix case where the there are no time blocks to determine in a constraint #920
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
For FI_Hydro_Reservoir in the EU case, there are no matches in the incoming flows, so there is nothing constraining the time block. In this case, it uses 1 as time_block_start and num_timesteps and tmie_block_end of the single block.
abelsiqueira
force-pushed
the
fix-highest-in
branch
from
d2cc296 to
bdf94ca
Compare
4 tasks
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #920 +/- ##
=======================================
Coverage 99.17% 99.17%
=======================================
Files 29 29
Lines 1206 1206
=======================================
Hits 1196 1196
Misses 10 10 ☔ View full report in Codecov by Sentry. |
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.
For FI_Hydro_Reservoir in the EU case, there are no matches in the incoming
flows, so there is nothing constraining the time block. In this case, it uses
1 as time_block_start and num_timesteps and tmie_block_end of the single
block.