Make the GeoAvailability constructor more flexible - #48
Merged
JulStraus merged 2 commits intoJan 6, 2026
Conversation
JulStraus
self-requested a review
January 5, 2026 07:51
JulStraus
reviewed
Jan 5, 2026
JulStraus
left a comment
JulStraus
left a comment
Member
There was a problem hiding this comment.
Looks good to me, but I think we can simultaneously update the docstring, see my comment. I unfortunately was not able to provide it as a suggestion.
JulStraus
approved these changes
Jan 6, 2026
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
2 participants
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.
This PR makes the
GeoAvailability(id, 𝒫::Array{Resource})constructor more flexible (enabling, e.g.,GeoAvailability("av", [ResourceCarrier("Power", 0.0)])).This also resolves a bug in EnergyModelsInputs.