Skip to content

Conversation

@jmarrec
Copy link
Collaborator

@jmarrec jmarrec commented Mar 12, 2025

Pull request overview

Pull Request Author

  • Model API Changes / Additions
  • Any new or modified fields have been implemented in the EnergyPlus ForwardTranslator (and ReverseTranslator as appropriate)
  • Model API methods are tested (in src/model/test)
  • EnergyPlus ForwardTranslator Tests (in src/energyplus/Test)
  • If a new object or method, added a test in NREL/OpenStudio-resources
  • If needed, added VersionTranslation rules for the objects (src/osversion/VersionTranslator.cpp)
  • Verified that C# bindings built fine on Windows, partial classes used as needed, etc.
  • All new and existing tests passes
  • If methods have been deprecated, update rest of code to use the new methods

Labels:

  • If change to an IDD file, add the label IDDChange
  • If breaking existing API, add the label APIChange
  • If deemed ready, add label Pull Request - Ready for CI so that CI builds your PR

Review Checklist

This will not be exhaustively relevant to every PR.

  • Perform a Code Review on GitHub
  • Code Style, strip trailing whitespace, etc.
  • All related changes have been implemented: model changes, model tests, FT changes, FT tests, VersionTranslation, OS App
  • Labeling is ok
  • If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
  • If feature, test running new feature, try creative ways to break it
  • CI status: all green or justified

@jmarrec jmarrec added component - Model Pull Request - Ready for CI This pull request if finalized and is ready for continuous integration verification prior to merge. IDDChange labels Mar 12, 2025
@jmarrec jmarrec self-assigned this Mar 12, 2025
@ci-commercialbuildings
Copy link
Collaborator

ci-commercialbuildings commented Mar 12, 2025

Copy link
Collaborator

@joseph-robertson joseph-robertson left a comment

Choose a reason for hiding this comment

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

Looks pretty complete to me. Just a (unrelated) question.

m_ignoreTypes.push_back(model::ModelObjectList::iddObjectType());
m_ignoreTypes.push_back(model::Node::iddObjectType());
m_ignoreTypes.push_back(model::OutputControlReportingTolerances::iddObjectType());
m_ignoreTypes.push_back(model::OutputControlResilienceSummaries::iddObjectType());
Copy link
Collaborator

Choose a reason for hiding this comment

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

Unrelated to this PR, but... should other OutputControl objects be in this list?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes. OutputSchedules too for eg.

I don't know who uses SDD these days to be honest, and I'll happily just ignore this until someone complains about the warnings

@jmarrec jmarrec merged commit c25aa50 into develop Mar 13, 2025
4 of 6 checks passed
@jmarrec jmarrec deleted the 5355-OutputControlResilienceSummaries branch March 13, 2025 11:35
jmarrec added a commit that referenced this pull request Mar 20, 2025
jmarrec added a commit that referenced this pull request Apr 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component - Model IDDChange Pull Request - Ready for CI This pull request if finalized and is ready for continuous integration verification prior to merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

E+ 25.1.0: Wrap OutputControl:ResilienceSummaries

4 participants