Closed yujiex closed 9 months ago
We really do need to figure out a way to include default fields past min-fields so that we can avoid these object specific corrections.
We really do need to figure out a way to include default fields past min-fields so that we can avoid these object specific corrections.
Indeed. Would it be possible to just fill everything instead of constraint by min-field? Is min-field mostly designed for those expandable objects? Not sure if we could identify those and fill values for other objects
Issue overview
In the object
ZoneHVAC:TerminalUnit:VariableRefrigerantFlow
, theMaximum Outdoor Dry-Bulb Temperature for Supplemental Heater Operation
is not filled with the default value if it's not present in the object, as the min-field=19 does not cover this field. This would mean if the line corresponding to "Maximum Outdoor Dry-Bulb Temperature for Supplemental Heater Operation" is present and the user didn't specify a value for it, the supplemental heater will turn off at 21C, but if this line is not present, then the supplemental heater will turn off at 0C.The issue is examined with two files adapted from VariableRefrigerantFlow_wSuppHeater_5Zone.idf. The capacity of TU1 VRF DX Heating Coil is changed from autosize to 500 (smaller than the demand) so that supplemental coil is needed for longer period. The runperiod is changed to 1/1 to 2/4.
The TU1 looks like this.
In this case, the supplemental heating coil turns off at 0C
Then the supplemental turn-off temperature is above 0C (it's 21C).
Details
Some additional details for this issue (if relevant):
Checklist
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.