Does OS 2.2.0 write the ideal load air system object to IDF file after E+ measures are executed?

edit

[Update March 2nd, 2018]:

The Ideal Loads Options measure is now available on BCL and on the Unmet Hours openstudio-measures Github.

If you want to run it for OpenStudio version <=1.14, there is a toggle in the measure.rb file to set it to edit ZoneHVAC:IdealLoadsAirSystem objects instead of HVACTemplate:Zone:IdealLoadsAirSystem objects.

The GitHub issue is closed, and the OpenStudio team will stay with the OS v2 series order of operations: EnergyPlus Measures -> Expand Objects -> Pre-Process

[Update October 5th, 2017]:

In OS v1 series, the order of operations is: Expand Objects -> EnergyPlus Measures -> Pre-Process

In OS v2 series, the order of operations is: EnergyPlus Measures -> Expand Objects -> Pre-Process

HVACTemplate objects, including HVACTemplate:Zone:IdealLoadsAirSystem objects, are translated into EnergyPlus objects (ZoneHVAC:IdealLoadsAirSystem objects) in the Expand Objects step.

This means EnergyPlus measures in OS v2.+ can't include any get calls to an object formed from expanding an HVACTemplate object because they don't exist yet.

The issue is that the workspace.getObjectsByType("ZoneHVAC:IdealLoadsAirSystem".to_IddObjectType) call in the measure script correctly returns ZoneHVAC:IdealLoadsAirSystem objects in OS v1.14, but returns an empty array in OS v2.2. The measure was written with OS v1.14.

I've submitted this as an issue. I'll update once I know more.

EnergyPlus Measures are executed after any OpenStudio Measures are applied to the Model and the Model has been forward translated to IDF. If you checked the Ideal Air Loads boxes for Thermal Zones then they should be in the IDF that the EnergyPlus Measure is working on.