Fix 5ZoneNightVent3.idf, and test FanPerformance:NightVentilation#11595
Fix 5ZoneNightVent3.idf, and test FanPerformance:NightVentilation#11595joseph-robertson wants to merge 10 commits into
Conversation
|
Looks good. |
|
The notes toward the beginning of the test file with This would certainly explain the indifference described in #11475 and the unmethours link, but it's still not clear whether the statement is true because there is truly no benefit or whether there is an underlying bug. I think intuitively you'd expect at least some benefit given the scenario. After some digging (i.e., adjusting night ventilation's schedules, limits, control zones, etc., and fan performance's total efficiency, pressure rise, etc.), it doesn't look like any combination actually affects the zone air temperature during the period when night ventilation is available. Maybe there are some key output variables to compare with 5ZoneNightVent2.idf's use of |
| AirTerminal:SingleDuct:VAV:Reheat, | ||
| SPACE1-1 VAV Reheat, !- Name | ||
| FanAvailSched, !- Availability Schedule Name | ||
| AlwaysOn, !- Availability Schedule Name |
There was a problem hiding this comment.
This is the fix to see nonzero airflow on the demand side of the loop during night ventilation.
See https://unmethours.com/question/103089/how-to-model-night-purge/ for more information.
There was a problem hiding this comment.
This does reveal an issue with system control that was not noticed until now. This example file shows that the TU availability schedule affects night cycle operation, and system operation for that matter if the TU avail sch was more restrictive than the parent and fan avail schedules. In a parent object (e.g., UnitarySystem) the fan is controlled based on parent availability schedule and fan availability schedule. It appears that TU availability schedule also matters (and there are multiple TUs for air systems, at least 1 would need to be available). This was never noticed before maybe because TU avail schedules are typically always on or at least using the least restrictive schedule or maybe because night ventilation/cycle is used less often.
There was a problem hiding this comment.
I'm throwing out a possible fix of TUs don't have avail schedules, they are always ON/available. Would that break anything? Would that restrict anything? Would that have less flexibility than is provided now?
| \object-list FansCVandVAV | ||
| \object-list FansComponentModel |
There was a problem hiding this comment.
The docs say "At this time, it can be used with Fan:ConstantVolume, Fan:VariableVolume, Fan:ZoneExhaust, Fan:OnOff and Fan:SystemModel fans, but not with Fan:ComponentModel fans."
| ! object. We ventilate the building in the early morning hours. | ||
| ! The runperiod is a summer week in Fresno. We assume a ventilation rate of 1/3 the | ||
| ! supply air design value and adjust the night ventilation fan performance | ||
| ! (FanPerformance:NightVentilation) object inputs accordingly. |
There was a problem hiding this comment.
This did not get updated starting with v8.7.0 when Fan:SystemModel was introduced and this test file was updated Fan:VariableVolume/FanPerformance:NightVentilation -> Fan:SystemModel.
| add_simulation_test(IDF_FILE 5ZoneNightVent1.idf EPW_FILE USA_CA_Fresno.Air.Terminal.723890_TMY3.epw) | ||
| add_simulation_test(IDF_FILE 5ZoneNightVent2.idf EPW_FILE USA_CA_Fresno.Air.Terminal.723890_TMY3.epw) | ||
| add_simulation_test(IDF_FILE 5ZoneNightVent3.idf EPW_FILE USA_CA_Fresno.Air.Terminal.723890_TMY3.epw) | ||
| add_simulation_test(IDF_FILE 5ZoneNightVent4.idf EPW_FILE USA_CA_Fresno.Air.Terminal.723890_TMY3.epw) |
There was a problem hiding this comment.
Bring back the original night ventilation test file using FanPerformance:NightVentilation -- without it, this object is not tested anywhere.
|
|
There was a problem hiding this comment.
Pull request overview
This PR addresses the reported night ventilation example problem in 5ZoneNightVent3.idf and reintroduces a companion example (5ZoneNightVent4.idf) to exercise FanPerformance:NightVentilation using a Fan:VariableVolume, along with corresponding IDD and documentation updates.
Changes:
- Fix
5ZoneNightVent3.idfnight ventilation behavior by ensuring VAV terminals remain available during night ventilation and by aligning the example narrative withFan:SystemModel. - Add
5ZoneNightVent4.idfand register it as a simulation test to coverFanPerformance:NightVentilationwithFan:VariableVolume. - Update the IDD object-list restrictions for
FanPerformance:NightVentilation, plus related Input Output Reference text.
Reviewed changes
Copilot reviewed 6 out of 7 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| testfiles/CMakeLists.txt | Adds a simulation test entry for the new 5ZoneNightVent4.idf. |
| testfiles/5ZoneNightVent4.idf | New example file using Fan:VariableVolume + FanPerformance:NightVentilation for night ventilation testing. |
| testfiles/5ZoneNightVent3.idf | Adjusts terminal availability and adds an AlwaysOn schedule; updates example narrative for Fan:SystemModel. |
| src/EnergyPlus/SystemAvailabilityManager.cc | Removes an unnecessary using namespace DataAirLoop; within night ventilation availability manager logic. |
| idd/Energy+.idd.in | Updates FanPerformance:NightVentilation allowed fan object-lists. |
| doc/input-output-reference/src/overview/group-system-availability-managers.tex | Minor wording tweak clarifying indoor/outdoor temperature difference description. |
| doc/input-output-reference/src/overview/group-fans.tex | Updates narrative/examples for FanPerformance:NightVentilation and cross-references. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ! | ||
| ! Simulation Location/Run: FRESNO_CA_USA TMY2-93193, 2 design days, 1 run period, | ||
| ! Run Control executes the run period using the weather file | ||
| ! |
There was a problem hiding this comment.
Only flagged because this file is new. The others don't have this update. Seems unnecessary.
|
|
|
rraustad
left a comment
There was a problem hiding this comment.
This looks good to me. Anything else can be a follow up issue.

Pull request overview
Description of the purpose of this PR
Pull Request Author
Reviewer