Skip to content
New issue

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

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

Already on GitHub? # to your account

Building Energy Standards Exterior Lighting Data Update #1896

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

leijerry888
Copy link
Collaborator

Updates have been made to the Building Energy Standards Data repository, see here. This pull request was automatically generated.

@lymereJ lymereJ marked this pull request as draft February 18, 2025 05:18
@lymereJ lymereJ changed the title Building Energy Standards Data Update Building Energy Standards Exterior Lighting Data Update Feb 18, 2025
@lymereJ lymereJ marked this pull request as ready for review February 24, 2025 18:48
@lymereJ lymereJ requested a review from mdahlhausen February 24, 2025 18:48
occupancy_setback_reduction = exterior_lighting_properties['occupancy_setback_reduction']
end
else
unless ['90.1-2004', '90.1-2007', 'DOE Ref Pre-1980', 'DOE Ref 1980-2004', 'DEER 1985', 'DEER 1996', 'DEER 2003', 'DEER 2007', 'DEER Pre-1975'].include?(template)
Copy link
Collaborator

Choose a reason for hiding this comment

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

make an inclusive criteria, not an exclusive one. There are several other standards ignored here.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Which ones are missing? I can certainly do that but there are a lot of applicable ones as well.

Copy link
Collaborator

Choose a reason for hiding this comment

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

other DEER versions, the NZE templates. I'm wondering if this should go back to being something in the standard fields? If it toggles on the standard, it should probably go in there.

Copy link
Collaborator

Choose a reason for hiding this comment

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

What other DEER versions? I see that the ones not listed there are using 0.3. Same for NZE. I'm not sure I understand what you mean by being in the standard fields, are you able to give an example?

}
exterior_lighting_parking_req = standards_lookup_table_first(table_name: 'exterior_lighting', search_criteria: search_criteria)
power = exterior_lighting_parking_req['allowance']
if exterior_lighting_parking_req['allowance_unit'] == 'W'
Copy link
Collaborator

Choose a reason for hiding this comment

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

in what instance is the allowance in watts?

Copy link
Collaborator

Choose a reason for hiding this comment

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

One example is the base allowance.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Makes sense for base allowance. It seems like this switch statement applies to all lighting types. A lot of duplicate code. It's not necessary in parking and most others, because all standard entries are in W/ft2. I can handle the cleanup unless there is a way you'd prefer to do it.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I removed the statements and also clarified the names of the definitions to be more in line with the inputs.

Copy link
Collaborator

@mdahlhausen mdahlhausen left a comment

Choose a reason for hiding this comment

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

I have another major exterior lighting module change I'm working on. Address the minor comments, and I'll see if it makes more sense to merge this PR into mine or vice-versa.

@mdahlhausen mdahlhausen mentioned this pull request Feb 25, 2025
16 tasks
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants