Update Baseline for scenario when Proposed has no cooling

[joesinger12]

This issue surfaced during review of Issue 2249.

DR - Since this design does not have cooling, I wouldn't expect that the bug identified in issue 2225 would impact this model. The baseline for the residential units is still FPFC, but per the change you and Roger made for v2.1, there is no cooling Tstat schedule. I ran the model and in the res spaces, there is not cooling energy, and the fan energy seems reasonable.

After making the fixes I recommend below, the model illustrates a fair amount of cooling credit. This appears to be because the the flr-by-flr corridor systems (System 5) are cooling the corridors, despite the fact that the corridor zones have no cooling T-stat schedule defined. This illustrates a concern when we started v3.0 development for modeling the baseline when the proposed has no cooling; i.e. zones with no cooling simply omit the cooling Tstat schedule.

Based on what I am seeing in this model; this approach doesn't work if a multizone system only serves one zone... One potential solution is to set the cooling capacity of the baseline system to 1 if the proposed design has been designed w/o cooling and if the baseline is a multizone system that only serves one zone. In v3.0, the "proposed has no cooling" scenario will be identified by the user as 'HasHtgOnly =1', but in v2.1, there is no workaround to this compliance credit unless users model a dummy cooling system.

Reported by: joesinger12

Original Ticket: cbecc-com/tickets/2275

[joesinger12]

• Milestone: Com2019.1.0 --> ComDevIssue

Original comment by: joesinger12

[joesinger12]

• Milestone: ComDevIssue --> CBECC2022DevIssues

Original comment by: joesinger12