Enforce full distribution of high temp radiant energy to surfaces and people

[RKStrand]

Pull request overview

This pull request includes the code fix, unit test, and minor documentation mod for a problem in the high temperature radiant heater code. In the code, a warning message was produced when the user did not assign all of the radiant energy emitted from the radiant heater to surfaces or people in a space. The code noted that the sum did not add up to unity and produced the warning but then simply continued to simulate things. This resulted in a loss of energy that could be up to 100% of the radiant energy. This was discovered by a user and a change was request. Now, the code will produce a severe warning and will also produce additional information telling the user what was processed and that this is not allowed. The documentation was also modified to clarify this as well. This fix applies to all high temperature radiant heater types and was logged as GitHub Issue #4324.

Work Checklist

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

• [ x ] Title of PR should be user-synopsis style (clearly understandable in a standalone changelog context)
• [ x ] At least one of the following appropriate labels must be added to this PR to be consumed into the changelog:
  • Defect: This defect is logged as ZoneHVAC:HighTemperatureRadiant - No radiant receiving surfaces and no radiant to people or GitHub Issue ZoneHVAC:HighTemperatureRadiant - No radiant receiving surfaces and no radiant to people #4324.

Review Checklist

This will not be exhaustively relevant to every PR.

• Code style (parentheses padding, variable names)
• Functional code review (it has to work!)
• If defect, results of running current develop vs this branch should exhibit the fix
• CI status: all green or justified
• Performance: CI Linux results include performance check -- verify this
• Unit Test(s)
• C++ checks:
  • Argument types
  • If any virtual classes, ensure virtual destructor included, other things
• n/a IDD changes:
• n/a If new idf included, locally check the err file and other outputs
• Documentation changes in place
• Changed docs build successfully
• n/a ExpandObjects changes?
• n/a If output changes, including tabular output structure, add to output rules file for interfaces