VRF heating fluid control heating: add SC adjustment for high demand case

[yujiex]

Pull request overview

• Fixes VRF fluid control heating: lacking coil capacity adjustment that increases capacity #10335

The following shows the existing logic in ControlVRFIUCoil. The yellow boxes indicates the possible position of the control target (the minimum of the two: indoor unit output (a reflection of zone demand) and coil capacity limit imposed by function limitTUCapacity so that total indoor unit output doesn't exceed the condenser capacity.

The PR implements the SC adjustment in the high-demand case.

The effect of adding this adjustment is shown in the following comparison. When the "Rated Evaporative Capacity" = coil "Rated Total Heating Capacity" = coil "Rated Total Cooling Capacity" = 10,000 or 15,000, before the adjustment, the subcooling degree stays at the user-input "Indoor Unit Reference Subcooling". After adding the adjustment, subcooling degree can further adjust to alter the coil capacity.

NOTE: ENHANCEMENTS MUST FOLLOW A SUBMISSION PROCESS INCLUDING A FEATURE PROPOSAL AND DESIGN DOCUMENT PRIOR TO SUBMITTING CODE

Pull Request Author

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

• 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

Reviewer

This will not be exhaustively relevant to every PR.

• 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

[nrel-bot-3]

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

[nrel-bot-2]

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

[nrel-bot]

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

[nrel-bot-2]

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

[nrel-bot]

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

[nrel-bot]

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

[nrel-bot-3]

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

[nrel-bot]

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

[nrel-bot-2]

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

[nrel-bot-2c]

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

[nrel-bot-2c]

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