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.

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 Rule6-11.md #1536

Open
wants to merge 1 commit into
base: feature/ashrae9012022
Choose a base branch
from
Open

Conversation

KarenWGard
Copy link
Collaborator

No description provided.

**Rule ID:** 6-11
**Rule Description:**Where retail display lighting is included in the proposed building design the display lighting additional power shall be less than or equal to the limits established by Section 9.5.2.2(b)
**Rule Assertion:** Proposed RMD = expected value
**Appendix G Section:** Table 9.5.2.2
Copy link
Collaborator

@claperle claperle Nov 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recommend including the Appendix G section that triggers this requirement as I think this is a semi-grey area in Appendix G and reading this without the App G reference is a little mind boggling as to why this would be required for the proposed. I recall discussing it previously, based on my memory, I think we all decided that it is required because of Section G1.2.1b.1 because it says "Tables G3.7-1 and G3.7-2 and the methodology described in Section 9.5.2". Is that correct?

- look at each interior lighting: `for interior_lighting in space.interior_lighting:`
- if the interior lighting purpose_type is RETAIL_DISPLAY, set applicable to true - we don't go to the rule logic for each interior lighting because the evaluation context is at the space level: `if interior_lighting.purpose_type == "RETAIL_DISPLAY": applicable = true`
- if the boolean applicable is true, continue to rule logic: `if applicable: CONTINUE TO RULE LOGIC`
- otherwise, rule is not applicable: `else: RULE NOT APPLICABLE`
Copy link
Collaborator

@claperle claperle Nov 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Section G1.2.1b. states that the building area or space by space method can be used in this determination. What if they are using the building area method for the comparison (G1.2.1b.2)? This does not appear to accountted for and not sure there is anything in the schema that would allow us to figure that out. With the building area method there are no additional allowances for retail display lighting. I need to think through this some more as I don't have a suggestion.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed on call, 6-1 does this check on the proposed. Add fucntions or modify 6-1 so that it checks if it complies using building area method. If not or data is not available to evaluate then check the space by space method including the retail allowances.

- look at each space: `for space in building_segment...spaces:`
- set a boolean called applicable to false: `applicable = false`
- set lighting_space_type equal to the space.lighting_space_type: `lighting_space_type = space.lighting_space_type`
- if the lighting_space_type is NULL, set the lighting_space_type equal to the building_segment_lighting_type: `if lighting_space_type == NULL: lighting_space_type = building_segment_lighting_type`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am confused as to why the space type is set equal to the building area type since they are different lists. Can you help me understand. It did not become apparent in reviewing the RDS.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These steps with the building area type can likely be removed

- if the boolean applicable is true, continue to rule logic: `if applicable: CONTINUE TO RULE LOGIC`
- otherwise, rule is not applicable: `else: RULE NOT APPLICABLE`

## Rule Logic:
Copy link
Collaborator

@claperle claperle Nov 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The formatting on this section does not appear to follow the typical markdown conventions we have been using. I am not sure of the reason exactly but for some reason this entire section shows in blue. View file to see what I mean more clearly.

- set a boolean called applicable to false: `applicable = false`
- set lighting_space_type equal to the space.lighting_space_type: `lighting_space_type = space.lighting_space_type`
- if the lighting_space_type is NULL, set the lighting_space_type equal to the building_segment_lighting_type: `if lighting_space_type == NULL: lighting_space_type = building_segment_lighting_type`
- if the lighting space type is a Sales Area, look at each InteriorLighting object in the model: `if lighting_space_type == "SALES AREA":`
Copy link
Collaborator

@claperle claperle Nov 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to think through handling space types without retail allowances. I guess the RDS that checks for compliance with G1.2.1b would include the retail display lighting objects when calculating the LPD for all space types except SALES AREA, can you confirm this is how the RDSs work together?

**Rule Assertion:**
- Case 1: If the proposed_interior_display_W is less than the minimum, then PASS: `if(proposed_interior_display_W < minimum_retail_display_W): PASS`
- Case 2: Otherwise, if the proposed_interior_display_W is greater than maximum_retail_display_W, then FAIL: `elif proposed_interior_display_W > maximum_retail_display_W: FAIL`
- Case 3: All other cases UNDETERMINED and provide note: `else: UNDETERMINED; note = "The RCT could not determine whether the proposed retail display lighting power is correctly modeled based on the result of the formula given by ASRAE 90.1 9.5.2.2(b)."`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested note: "It could not be determined whether the proposed retail display lighting power is less than or equal to the allowance calculated according to the formulas in ASHRAE 90.1 Section 9.5.2.2(b)."

- if the interior lighting purpose_type is RETAIL_DISPLAY, add the lighting wattage to proposed_interior_display_W: `if interior_lighting.purpose_type == "RETAIL_DISPLAY": proposed_interior_display_W = proposed_interior_display_W + interior_lighting.power_per_area * space.floor_area`

**Rule Assertion:**
- Case 1: If the proposed_interior_display_W is less than the minimum, then PASS: `if(proposed_interior_display_W < minimum_retail_display_W): PASS`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be less than or equal to, right?



**Notes:**
1. Is the lighting space type check necessary because we are checking the interior_lighting.purpose_type to be RETAIL_DISPLAY?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is based on the language in Section 9.5.2.2 b where it says "For lighting equipment installed in sales areas"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants