Skip to content

Add OpenRESV library to repos.json#75

Open
lvanfretti wants to merge 1 commit into
OpenModelica:masterfrom
lvanfretti:add-openresv
Open

Add OpenRESV library to repos.json#75
lvanfretti wants to merge 1 commit into
OpenModelica:masterfrom
lvanfretti:add-openresv

Conversation

@lvanfretti

Copy link
Copy Markdown

OpenRESV (Open Instance Renewable Energy Source Validation) is an open-source Modelica library focused on modeling and validation of WECC-based renewable energy models. It includes customized renewable energy source models validated against Power Hardware-in-the-Loop (PHIL) experiments, along with a minimal set of power system components from OpenIPSL.

Support level set to experimental. The library is designed to run in OpenModelica and the README includes step-by-step instructions for doing so.

Copilot AI review requested due to automatic review settings June 15, 2026 15:56

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a new repository entry to the repo registry so the tooling can discover and classify OpenRESV releases.

Changes:

  • Register OpenRESV with GitHub location and extra search paths.
  • Define branch mapping and support policy by version range.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread repos.json
Comment on lines +1092 to +1096
"support": [
["prerelease", "noSupport"],
[">=1.0.0", "experimental"],
["*", "obsolete"]
]

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the review! The ["*", "obsolete"] wildcard catch-all is the established convention used consistently across all entries in repos.json (see e.g. OpenHPL, NeuralNetwork, ScalableTestGrids, BidiDCDC, etc.). Changing it to an explicit range for this entry alone would be inconsistent with the rest of the file. Happy to follow the maintainers' preference if they'd like a different approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants