Repository navigation
fix: reject demand and solar forecasts above 100 MWh per step - #325
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or 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
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.
Follows #321.
About 90 requests a day still end Not Solved on revision 63. All come from one installation whose household profile carries 1e9 to 1.5e16 Wh in nearly every step, repeating every 96 slots. Its grid has no import limit, so the model is feasible, CBC does not prove the probe infeasible and #321 does not apply. The split hands it to HiGHS, which returns no solution for such coefficients.
gtandftnow carrymaximum: 1e8Wh per step in the request schema, so such a request is a 400 naming every offending step (time_series.gt.N), like the other field checks