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

Add misc appliances to panel load calc #1323

Open
wants to merge 5 commits into
base: ll/test_panel_cap
Choose a base branch
from

Conversation

lixiliu
Copy link
Contributor

@lixiliu lixiliu commented Nov 18, 2024

Pull Request Description

Assign the following miscellaneous permanently connected appliances to homes for NEC panel load calculations:

  • Microwave: 100% of homes, power level based on the number of occupants

    • Sizing (in cu ft) based on Whirlpool's microwave buying guide, then power is assigned to each cu ft class based on general search

      Occupants Size (cu ft) Power (W)
      0 - 2 0.5 - 0.9 900
      3 - 4 1.0 - 1.6 1100
      4+ 1.7 - 2.2 1250
  • Garbage disposal: 52% of homes (AHS 2013), power level based on the number of occupants

    • Power rating estimated based on average load amperage (x 120V), not horsepower rating as they appear to consume more power

    • Power rating based on InSinkErator product labels

    • Sizing based on Lowe's garbage disposal buying guide

      Occupants Size (HP) Avg Load (A) Power (W)
      0 - 1 5.6 672
      2 - 3 ½ 6.3 756
      4 - 5 ¾ 9.5 1140
      5+ 1 10.2 1224
  • Garage door opener: assign one ½ HP if home has a garage, regardless of the number of garage

    • Power rating converted from horsepower rating at 1 mech HP = 745.7 W

@afontani @JLReyna - should this be based on occupants or bedrooms, is there a conversion between the two?

Related Pull Requests

[related PRs from different repositories]

Related Issues

[What issue(s) is the PR addressing]

Checklist

Required:

Optional (not all items may apply):

# Assume all homes have a microwave
if args[:geometry_unit_num_occupants] <= 2
microwave_power = 900 # W, small, <= 0.9 cu ft
elsif args[:geometry_unit_num_occupants] <= 4
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@joseph-robertson - is this okay or do I need to define the condition as args[:geometry_unit_num_occupants] > 2 && args[:geometry_unit_num_occupants] <= 4?

Copy link
Contributor

Choose a reason for hiding this comment

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

Looks right to me.

Should Occupants=0 assign 900 W?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think so. Microwave exists in unoccupied homes too.
I am also wondering if we should do this based on # of bedrooms instead. Is there a conversion we can use between occupants and bedrooms?

garage_door_power = 0
else
# Assume one automatic door opener if has garage, regardless of no. garages
garage_door_power = 373 # W, 1/2 HP (1 mech HP = 745.7 W)
Copy link
Contributor

Choose a reason for hiding this comment

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

I had this built into OS-HPXML defaults: https://github.com/NREL/OpenStudio-HPXML/blob/electric_panel/HPXMLtoOpenStudio/resources/defaults.rb#L6128-L6130

But maybe it makes sense to do the assignment here instead.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, this is more of a ResStock assumption

# Assume all homes have a microwave
if args[:geometry_unit_num_occupants] <= 2
microwave_power = 900 # W, small, <= 0.9 cu ft
elsif args[:geometry_unit_num_occupants] <= 4
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks right to me.

Should Occupants=0 assign 900 W?

@JLReyna
Copy link
Member

JLReyna commented Nov 20, 2024

@lixiliu - in response to your question, the Occupants.tsv has a dependency on Bedrooms.tsv. I don't actually think we should have a dependency on either for garage doors. To have multiple openers (or differently sized openers), you'd be assuming some sort of factor driving the increase. I'd probably argue Geometry Floor Area if we were to choose something, but I don't think we know enough to develop that. Size of the garage (1 car, 2 car, 3 car) would be the clearest indicator, but even that doesn't mean increases in the opener. So long winded way to say I don't think this should have dependencies. @afontani do you agree?

@lixiliu
Copy link
Contributor Author

lixiliu commented Nov 20, 2024

@lixiliu - in response to your question, the Occupants.tsv has a dependency on Bedrooms.tsv. I don't actually think we should have a dependency on either for garage doors. To have multiple openers (or differently sized openers), you'd be assuming some sort of factor driving the increase. I'd probably argue Geometry Floor Area if we were to choose something, but I don't think we know enough to develop that. Size of the garage (1 car, 2 car, 3 car) would be the clearest indicator, but even that doesn't mean increases in the opener. So long winded way to say I don't think this should have dependencies. @afontani do you agree?

Thanks @JLReyna - and apologies for the confusion, the question is really for assigning microwave and garbage disposal, not garage door (and I completely agreed that there should not be a dependency to occupants there). There are market guidance on the sizing of microwave and garbage disposal based on household size, which I am using currently. But using occupants instead of bedrooms means we may have undersized equipment for vacant homes which have 0 occupants. So instead of using occupants directly, can we infer typical occupancy based on bedrooms and size based on that?

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

Successfully merging this pull request may close these issues.

3 participants