Skip to content

Refactor array-based input code to use key-based input (problem cases)#11536

Draft
jasondegraw wants to merge 20 commits intodevelopfrom
no-array-input-problems
Draft

Refactor array-based input code to use key-based input (problem cases)#11536
jasondegraw wants to merge 20 commits intodevelopfrom
no-array-input-problems

Conversation

@jasondegraw
Copy link
Copy Markdown
Member

Pull request overview

This is a follow-up PR to previous PRs doing input refactoring. This PR will stay in draft for a bit as I collect problematic cases, so far there are two that needed to be separated out (one due to operator error, the other due to MTR diffs).

Pull Request Author

  • Title of PR should be user-synopsis style (clearly understandable in a standalone changelog context)
  • Label the PR with at least one of: Defect, Refactoring, NewFeature, Performance, and/or DoNoPublish
  • Pull requests that impact EnergyPlus code must also include unit tests to cover enhancement or defect repair
  • Author should provide a "walkthrough" of relevant code changes using a GitHub code review comment process
  • If any diffs are expected, author must demonstrate they are justified using plots and descriptions
  • If changes fix a defect, the fix should be demonstrated in plots and descriptions
  • If any defect files are updated to a more recent version, upload new versions here or on DevSupport
  • If IDD requires transition, transition source, rules, ExpandObjects, and IDFs must be updated, and add IDDChange label
  • If structural output changes, add to output rules file and add OutputChange label
  • If adding/removing any LaTeX docs or figures, update that document's CMakeLists file dependencies
  • If adding/removing any output files (e.g., eplustbl.*)
    • Update ..\scripts\Epl-run.bat
    • Update ..\scripts\RunEPlus.bat
    • Update ..\src\EPLaunch\ MainModule.bas, epl-ui.frm, and epl.vbp (VersionComments)
    • Update ...github\workflows\energyplus.py

Reviewer

  • Perform a Code Review on GitHub
  • If branch is behind develop, merge develop and build locally to check for side effects of the merge
  • 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
  • Check that performance is not impacted (CI Linux results include performance check)
  • Run Unit Test(s) locally
  • Check any new function arguments for performance impacts
  • Verify IDF naming conventions and styles, memos and notes and defaults
  • If new idf included, locally check the err file and other outputs

@github-actions
Copy link
Copy Markdown

⚠️ Regressions detected on ubuntu-24.04 for commit e5af094

Regression Summary
  • MDD: 6
  • MTD: 7
  • Table String Diffs: 5
  • BND: 9
  • RDD: 1
  • EIO: 2

@github-actions
Copy link
Copy Markdown

⚠️ Regressions detected on macos-14 for commit e5af094

Regression Summary
  • MDD: 6
  • MTD: 7
  • Table String Diffs: 5
  • BND: 9
  • RDD: 1
  • EIO: 2

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