Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
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.
| | 2 | No.2 Revision |
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.
[UPDATE]:
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.
| | 3 | No.3 Revision |
The issue is that the [Update March 2nd, 2018]:workspace.getObjectsByType("ZoneHVAC:IdealLoadsAirSystem".to_IddObjectType) call in the
The Ideal Loads Options measure script correctly returns 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 in OS v1.14, but returns an empty array in OS v2.2. The measure was written instead of HVACTemplate:Zone:IdealLoadsAirSystem objects.
The GitHub issue is closed, and the OpenStudio team will stay with OS v1.14.
I've submitted this as an issue. I'll update once I know more.
[UPDATE]: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.
