Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4-11_Update #1615

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

4-11_Update #1615

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0ad2262
Updated Case 3 outcome from UNDETERMINED to FAIL so that this rule wo…
claperle Jan 23, 2025
2611298
Fixed case numbering
claperle Jan 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/section4/4-11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@
**Rule Assertion:**
- Case 1: For each zone, hvac fan schedules match between the baseline and proposed and either single zone systems or multizone systems are both modeled in the baseline and proposed then PASS: `if schedule_mismatch == FALSE and system_type_match_baseline_proposed == TRUE: outcome == "PASS"`
- Case 2: For each applicable zone, elif there is a fan schedule mismatch but Section G3.1.1(c) appears to apply then undetermined: `elif schedule_mismatch == TRUE AND baseline_served_by_multizone == FALSE AND hvac_type_check == TRUE AND proposed_served_by_multizone == TRUE: outcome == "UNDETERMINED" and raise_message "THERE IS A FAN OPERATING SCHEDULE MISMATCH BETWEEN THE BASELINE AND PROPOSED BUT SECTION G3.1.1(c) APPEARS APPLICABLE. VERIFY MISMATCH IS APPROPRIATE PER SECTION G3.1.1(c) AND THAT THE FAN OPERATING SCHEDULE IN THE BASELINE IS IN ALIGNMENT WITH THE OCCUPANCY SCHEDULES."`
- Case 4: Else if, there is a schedule mismatch between the baseline and proposed then undetermined: `elif schedule_mismatch == TRUE: outcome == "UNDETERMINED" and raise_message "THERE IS A FAN SCHEDULE MISMATCH BETWEEN THE BASELINE AND PROPOSED RMDs FOR THE HVAC SYSTEM(S) SERVING THIS ZONE. FAIL UNLESS TABLE G3.1 SECTION 4 BASELINE COLUMN EXCEPTIONS #1, #2 or #3 IS APPLICABLE"`
- Case 3: Else (schedules match between the baseline and proposed), undertermined: `Else: outcome == "UNDETERMINED" and raise_message "FAN SCHEDULES MATCH BETWEEN THE BASELINE AND PROPOSED RMDs FOR THE HVAC SYSTEM(S) SERVING THIS ZONE. VERIFY THAT MATCHING SCHEDULES ARE APPROPRIATE IN THAT NONE OF THE SECTION 4 BASELINE COLUMN EXCEPTIONS #1, #2 or #3 ARE APPLICABLE"`
- Case 3: Else if, there is a schedule mismatch between the baseline and proposed then Fail: `elif schedule_mismatch == TRUE: outcome == "FAIL" and raise_message "THERE IS A FAN SCHEDULE MISMATCH BETWEEN THE BASELINE AND PROPOSED RMDs FOR THE HVAC SYSTEM(S) SERVING THIS ZONE. FAIL UNLESS TABLE G3.1 SECTION 4 BASELINE COLUMN EXCEPTIONS #1, #2 or #3 IS APPLICABLE"`
- Case 4: Else (schedules match between the baseline and proposed), undetermined: `Else: outcome == "UNDETERMINED" and raise_message "FAN SCHEDULES MATCH BETWEEN THE BASELINE AND PROPOSED RMDs FOR THE HVAC SYSTEM(S) SERVING THIS ZONE. VERIFY THAT MATCHING SCHEDULES ARE APPROPRIATE IN THAT NONE OF THE SECTION 4 BASELINE COLUMN EXCEPTIONS #1, #2 or #3 ARE APPLICABLE"`

**[Back](../_toc.md)**
Loading