Skip to content

Conversation

lymereJ
Copy link
Collaborator

@lymereJ lymereJ commented Aug 25, 2025

Pull request overview

Description of the purpose of this PR

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

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

@lymereJ lymereJ added the Defect Includes code to repair a defect in EnergyPlus label Aug 25, 2025
@lymereJ lymereJ added this to the EnergyPlus 25.2 milestone Aug 25, 2025
@nrel-bot-2
Copy link

@lymereJ @Myoldmopar it has been 28 days since this pull request was last updated.

@lymereJ lymereJ marked this pull request as ready for review October 3, 2025 02:19
@lymereJ lymereJ marked this pull request as draft October 3, 2025 02:29
@lymereJ lymereJ marked this pull request as ready for review October 3, 2025 04:32
Copy link
Collaborator Author

@lymereJ lymereJ left a comment

Choose a reason for hiding this comment

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

Code walk-through:

Comment on lines +457 to +459
if (state.dataSysVars->ReportDuringWarmup) {
OutputProcessor::ResetAccumulationWhenWarmupComplete(state);
}
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Use (unused) existing function to reset the meters when warmup is complete.

Comment on lines +10101 to +10105
EXPECT_NEAR(state->dataUnitarySystems->unitarySys[0].m_DesignCoolingCapacity, 24883.6371, 0.05);

// Check meter accumulation
// Lights are 1W so the meter should be 3600 [J] * 24 hours
EXPECT_TRUE(state->dataOutputProcessor->meters[4]->periodFinYrSM.Value == 3600 * 24);
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Piggy-back on an existing unit test; A 1 W light object is used to check that the meters are being reset.

@lymereJ
Copy link
Collaborator Author

lymereJ commented Oct 3, 2025

The defect file was updated to v25.2: defect_file_252.txt.

When using this branch, the results are the same whether ReportDuringWarmup is selected as input or not.

image

These are the same results that we get when using develop and ReportDuringWarmup isn't selected.

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

Labels

Defect Includes code to repair a defect in EnergyPlus

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Output:Diagnostics's ReportDuringWarmup option impact annual energy use

4 participants