NatLabRockies / NatLabRockies/OpenStudio
Allow Connector:Splitter and Connector:Mixer to be used to create bypass branch on AirLoopHVAC supply side
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 646
- Forks
- 237
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 10
Description
Enhancement Request
The EnergyPlus example file '5ZoneSupRetPlenRAB.idf' demonstrates how Connector:Splitter, Connector:Mixer, and Duct components can be used to create a supply-side bypass branch on an AirLoopHVAC. The HVAC-Diagram output of this file shows the following (labels not shown because of broken HVAC-Diagram in 9.5):

Connector:Splitter, Connector:Mixer, and Duct are all implemented in OpenStudio, however it appears that Connector:Splitter on an air loop forces a dual-duct configuration of that loop, and it doesn't seem that Connector:Mixer can be added anywhere.
This file uses SetpointManager:ReturnAirBypassFlow to set flow on the bypass loop. That object should be added to enable bypass operation.
Implementation should support creating/adding components to a branch before the Splitter and after the Mixer, and on any of the parallel branches between the two. SetpointManager:ReturnAirBypassFlow references the AirLoop (not a specific node).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the EnergyPlus example file 5ZoneSupRetPlenRAB.idf and the existing Connector:Splitter, Connector:Mixer, and Duct support in OpenStudio. Trace how AirLoopHVAC branches and SetpointManager:ReturnAirBypassFlow are represented; done means components can be placed before the Splitter, after the Mixer, and on parallel branches, with the bypass setpoint manager referencing the AirLoop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100