Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question
3

Why some attribute is not documented in OpenStudio SDK?

asked 2018-05-28 20:57:22 -0500

katsuya.obara's avatar

updated 2018-05-29 10:20:17 -0500

I am trying to change the attributes (highlighted by red color) in below image.
However when I look at the OpenStudio SDK, I cannot find attributes corresponding to the attributes I want to change by measure as shown bottom image.
Does anyone know whether I can change Zone Minimum Air Flow Input Method and Control For Outdoor Air by measure?

image description
image description

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
3

answered 2018-05-29 03:03:52 -0500

updated 2018-05-29 03:08:38 -0500

@MatthewSteen is linking to the right documentation.

To specifically answer your question though, your problem is that you're not looking at the same two objects:

  • In OS App, you are looking at a AirTerminalSingleDuctVAVNoReheat, where the methods are dutifully documented.
  • In the SDK documentation screenshot, you are looking at AirTerminalSingleDuctVAVHeatAndCoolNoReheat, which is not the same object and doesn't have these two methods.

Now, to give a bit of context of what these two methods actually do, since there aren't any function docstrings:

setZoneMinimumAirFlowInputMethod directly affects the E+ field Zone Minimum Air Flow Method. See the I/O reference guide for what this field does.

setControlForOutdoorAir doesn't exist in E+. This is a special convenience method offered by OpenStudio. What it does if set to "Yes" is to automatically fill the Design Specification Outdoor Air Object Name by looking at the ThermalZone that is served by this air terminal unit.(see ForwardTranslate source code here[1])


[1] Note: it looks like it takes only the DSOA from the first space in the ThermalZone, but rest assured that it does calculate an equivalent DSOA from all spaces that make the ThermalZone. Indeed, all spaces are initially combined into one at the beginning of the forward translation here in ForwardTranslator.cpp

edit flag offensive delete link more
4

answered 2018-05-28 21:28:17 -0500

updated 2018-05-28 21:30:31 -0500

Here are the links to the methods for the AirTerminalSingleDuctVAVNoReheat, which should be the same for the AirTerminalSingleDuctVAVHeatAndCoolNoReheat class.

In a measure it would look like...

objects = model.getAirTerminalSingleDuctVAVNoReheats

objects.each do |obj|
  obj.setZoneMinimumAirFlowInputMethod('FixedFlowRate')
  obj.setControlForOutdoorAir(false)
end
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Training Workshops

Careers

Question Tools

3 followers

Stats

Asked: 2018-05-28 20:57:22 -0500

Seen: 128 times

Last updated: May 29 '18