Revision history [back]

@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)

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.

@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)

@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