-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
create Rule1-6 #1532
Open
KarenWGard
wants to merge
4
commits into
develop
Choose a base branch
from
RDS/KJW/Rule_1-6
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
create Rule1-6 #1532
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
|
||
# Section 1 - Rule 1-6 | ||
|
||
**Rule ID:** 1-6 | ||
**Rule Description:** On-site renewable energy shall not be included in the baseline building performance. | ||
**Rule Assertion:** Baseline RMD = expected value | ||
**Appendix G Section:** G3.11 18 Baseline | ||
|
||
**Mandatory Rule:** True | ||
**Evaluation Context:** Each RMD | ||
**Function Call:** | ||
|
||
## Applicability Check: | ||
- All projects are applicable | ||
|
||
|
||
## Rule Logic: | ||
- get the baseline output schema: `output = B_RMD.output` | ||
- get the output instance: `output_instance = output.output_instance` | ||
- set a boolean has_renewables and set it to false: `has_renewables = false` | ||
- look at each end use result: `for end_use_result in output_instance.annual_end_use_results:` | ||
- check if the energy source for the end_use_result is "ON_SITE_RENEWABLES": `if end_use_result.energy_source == "ON_SITE_RENEWABLES":` | ||
- set has_renewables to true and continue to rule assertion: `has_renewables = true; CONTINUE TO RULE ASSERTION` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. maybe we could also check if the annual_site_energy_use >0 when the energy source = on site renewables There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. changed |
||
- if we get here without going to the rule assertion, continue to rule assertion: `CONTINUE TO RULE ASSERTION` | ||
|
||
**Rule Assertion:** | ||
- Case 1: If has_renewables is true, then FAIL: `if has_renewables == true: FAIL` | ||
- Case 2: otherwise, there are no renewables, PASS: `else: PASS` | ||
|
||
|
||
**Notes:** | ||
1. | ||
|
||
**[Back](../_toc.md)** | ||
|
||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should check this across each orientation, unless that is captured somewhere else. I know Jackson populated the schema for things that should match across the baseline orientations. Not sure if we also did this with with output schema.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JacksonJ-KC ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was not done for the output schema but it seems like a good idea to take the same approach of adding those to the schema yaml/json and having the same rule cover them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I addressed this by doing the following:
- look at each baseline model rotation:
for rotation in [B_RMD, B_RMD_90, B_RMD_180, B_RMD_270]:``