-
Notifications
You must be signed in to change notification settings - Fork 9
Move validation to Submodel classes #473
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix initial-capacity bounds and
.any()usage inStorageModel._validateThere are two intertwined issues in the storage validation:
Currently you compute:
If
minimum_capacity < maximum_capacity, this can easily yieldminimum_initial_capacity > maximum_initial_capacity, and your subsequent checks:will incorrectly flag valid
initial_charge_statevalues as “constraining the investment decision”.To represent the union of feasible initial charge states across the capacity range, these should be:
.any()As in other models, you’re using
.any()on array-like objects directly inifconditions:With xarray
DataArrays (or numpy arrays), these.any()calls yield arrays, andif <array>raises the usual ambiguous truth-value error.A safe version would be:
This fixes both the logical bounds and the xarray-related runtime errors, while also correcting the small “Chosse” typo in the messages.
🤖 Prompt for AI Agents