Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
(I hope I'm getting your question right).
Yes, you can edit a thermal zone's ideal loads air system attributes. But the system must be first instantiated, then linked to a thermal zone (a nice demo here) to be effective:
ideal_loads = OpenStudio::Model::ZoneHVACIdealLoadsAirSystem.new(model)
ideal_loads.addToThermalZone(thermal_zone)
ideal_loads.setHeatRecoveryType("Sensible")
ideal_loads.setSensibleHeatRecoveryEffectiveness(0.7)
(Ruby interacting with the OpenStudio SDK).
| | 2 | No.2 Revision |
(I hope I'm getting your question right).
Yes, you can edit a thermal zone's ideal loads air system attributes. But the system must be first instantiated, then linked to a thermal zone (a nice demo here) to be effective:edited (not autogenerated at runtime):
ideal_loads = OpenStudio::Model::ZoneHVACIdealLoadsAirSystem.new(model)
ideal_loads.addToThermalZone(thermal_zone)
ideal_loads.setHeatRecoveryType("Sensible")
ideal_loads.setSensibleHeatRecoveryEffectiveness(0.7)
(Ruby interacting with the OpenStudio SDK).
| | 3 | No.3 Revision |
(I hope I'm getting your question right).
Yes, you can edit a thermal zone's ideal loads air system attributes. But the system must be first instantiated, then linked to a thermal zone (a nice demo here) to be edited editable (not autogenerated at runtime):
ideal_loads = OpenStudio::Model::ZoneHVACIdealLoadsAirSystem.new(model)
ideal_loads.addToThermalZone(thermal_zone)
ideal_loads.setHeatRecoveryType("Sensible")
ideal_loads.setSensibleHeatRecoveryEffectiveness(0.7)
(Ruby interacting with the OpenStudio SDK).
| | 4 | No.4 Revision |
(I hope I'm getting EDIT: I allowed myself to slightly change the title to emphasize OpenStudio. Also edited my initial answer in response to your question right).comment below. If you search UMH, as well as OpenStudio and EnergyPlus GitHub issues, the approach appears something of a hot potato. I'll leave at that, and try to keep things to the point.
Yes, you Option A
thermal_zone.setUseIdealAirLoads(true)
... instructs OpenStudio to generate a HVACTemplate:Zone:IdealLoadsAirSystem object during forward translation. There are possibly other objects OpenStudio adds in the process, like OutputVariables - not sure.
One can always edit HVACTemplate:Zone:IdealLoadsAirSystem objects in the generated run/in.idf file, but heat recovery settings aren't (yet) available before ExpandObjects is finally executed. So in a thermal zone's nutshell, I don't believe it possible to edit ideal loads air system attributes. But the system must be first instantiated, then linked to a system heat recovery settings using this approach with OpenStudio.
It's worth running energyplus -x in.idf and checking the generated eplusout.expidf file. As detailed in the EnergyPlus IO Reference, the HVACTemplate:Zone:IdealLoadsAirSystem objects are commented out, while the file inherits new (expanded) IDF objects (search for "New objects created from ExpandObjects") including ZoneHVAC:IdealLoadsAirSystem, allowing one to edit heat recovery settings! It's worth noting what ExpandedObjects ended up adding ...
Option B
As an alternative, one can skip the HVACTemplate option altogether, and instead directly add an ideal loads air system to each thermal zone (a - a nice demo here) to be editable (not autogenerated at runtime)::
ideal_loads = OpenStudio::Model::ZoneHVACIdealLoadsAirSystem.new(model)
ideal_loads.addToThermalZone(thermal_zone)
ideal_loads.setHeatRecoveryType("Sensible")
ideal_loads.setSensibleHeatRecoveryEffectiveness(0.7)
(Ruby interacting One can edit other variables. One can always look up other bare bones minimum model requirements, such as space/spacetype inputs, thermostats, etc.
I find OpenStudio Resources very handy ...
More steps, yet more options to fine-tune. Preferred approach going forward, I think.
Hope this is clearer. There are certainly more experienced users with the OpenStudio SDK).
| | 5 | No.5 Revision |
EDIT: I allowed myself to slightly change the title to emphasize OpenStudio. Also edited my initial answer in response to your comment below. If you search UMH, as well as OpenStudio and EnergyPlus GitHub issues, the approach appears something of a hot potato. I'll leave at that, and try to keep things to the point.
Option A
thermal_zone.setUseIdealAirLoads(true)
... instructs OpenStudio to generate a HVACTemplate:Zone:IdealLoadsAirSystem object during forward translation. There are possibly other objects OpenStudio adds in the process, like OutputVariables - not sure.
One can always edit HVACTemplate:Zone:IdealLoadsAirSystem objects in the generated run/in.idf file, but heat recovery settings aren't (yet) available before ExpandObjects is finally executed. So in a nutshell, I don't believe it possible to edit ideal loads air system heat recovery settings using this approach with OpenStudio.
It's worth running energyplus -x in.idf and checking the generated eplusout.expidf file. As detailed in the EnergyPlus IO Reference, the HVACTemplate:Zone:IdealLoadsAirSystem objects are commented out, while the file inherits new (expanded) IDF objects (search for "New objects created from ExpandObjects") including ZoneHVAC:IdealLoadsAirSystem, allowing one to edit heat recovery settings! It's worth noting what ExpandedObjects ended up adding ...
Option B
As an alternative, one can skip the HVACTemplate option altogether, and instead directly add an ideal loads air system to each thermal zone - a nice demo here: (Line 27):
ideal_loads = OpenStudio::Model::ZoneHVACIdealLoadsAirSystem.new(model)
ideal_loads.addToThermalZone(thermal_zone)
ideal_loads.setHeatRecoveryType("Sensible")
ideal_loads.setSensibleHeatRecoveryEffectiveness(0.7)
One can edit other variables. One can always look up other bare bones minimum model requirements, such as space/spacetype inputs, (Line 469), thermostats, etc.
(Line 620), etc. - I find OpenStudio Resources very handy ...handy!
More steps, yet more options to fine-tune. Preferred approach going forward, I think.
Hope this is clearer. There are certainly more experienced users with OpenStudio vs HVAC templates + ExpandObjects - maybe they can chime in.
| | 6 | No.6 Revision |
EDIT: I allowed myself to slightly change the title to emphasize OpenStudio. Also edited my initial answer in response to your comment below. If you search UMH, as well as OpenStudio and EnergyPlus GitHub issues, the approach appears something of a hot potato. I'll leave it at that, and try to keep things to the stay on point.
Option A
thermal_zone.setUseIdealAirLoads(true)
... instructs OpenStudio to generate a HVACTemplate:Zone:IdealLoadsAirSystem object during forward translation. There are possibly other objects OpenStudio adds in the process, like OutputVariables - not sure.
One can always edit HVACTemplate:Zone:IdealLoadsAirSystem objects in the generated run/in.idf file, but heat recovery settings aren't (yet) available before ExpandObjects is finally executed. So in a nutshell, I don't believe it possible to edit ideal loads air system heat recovery settings using this approach with OpenStudio.
It's worth running energyplus -x in.idf and checking the generated eplusout.expidf file. As detailed in the EnergyPlus IO Reference, the HVACTemplate:Zone:IdealLoadsAirSystem objects are commented out, while the file inherits new (expanded) IDF objects (search for "New objects created from ExpandObjects") including ZoneHVAC:IdealLoadsAirSystem, allowing one to edit heat recovery settings! It's worth noting what ExpandedObjects ended up adding ...
Option B
As an alternative, one can skip the HVACTemplate option altogether, and instead directly add an ideal loads air system to each thermal zone - a nice demo here (Line 27):
ideal_loads = OpenStudio::Model::ZoneHVACIdealLoadsAirSystem.new(model)
ideal_loads.addToThermalZone(thermal_zone)
ideal_loads.setHeatRecoveryType("Sensible")
ideal_loads.setSensibleHeatRecoveryEffectiveness(0.7)
One can edit other variables. One can always look up other bare bones minimum model requirements, such as space/spacetype inputs (Line 469), thermostats (Line 620), etc. - I find OpenStudio Resources very handy!
More steps, yet more options to fine-tune. Preferred approach going forward, I think.
Hope this is clearer. There are certainly more experienced users with OpenStudio vs HVAC templates + ExpandObjects - maybe they can chime in.
