Translation of control zone list for availability manager night cycle

Issue overview

When forward translating availability manager night cycle objects, OpenStudio makes assumptions regarding the default control zones to include in the EnergyPlus input file. It appears that for the CycleOnAnyCoolingOrHeatingZone control type, some of these assumptions are limiting: Users should be able to model such objects with heating zone fan only zones specified but no heating control zones.

This is specifically the case when dealing with night cycle operation of VAV systems with parallel PIU terminal units where the desired behavior is to meet the load by running the terminal fan (central system fan is off).

Current Behavior

Currently, when not specified by the users, OpenStudio defaults both the heating control zones (heatingControlThermalZones) and heating zone fan only thermal zones (heatingZoneFansOnlyThermalZones) which prevents models to behave as described in the overview to happen: assigning zones to heatingControlThermalZones triggers the central system to come on during heating night cycle operations.

Expected Behavior

Users should be able to provide a list of zone under heating zone fan only (heatingZoneFansOnlyThermalZones) without having OpenStudio default the heating thermal zone (heatingControlThermalZones) to a list of all the zones served by the air loop.

Steps to Reproduce

defect_files.zip

Possible Solution

The code the default assumptions appears to be here.

Details

Some additional details about your environment for this issue (if relevant):

• Platform (Operating system, version): Windows 10
• Version of OpenStudio (if using an intermediate build, include SHA): 3.2.1

Context

This impacts the ASHRAE 90.1(-2019) Appendix G Baseline Automation feature of openstudio-standards. @dmaddoxwhite @mdahlhausen