Opened 4 years ago

Last modified 3 years ago

#975 new task

Expose people schedule as an input

Reported by: ewilson Owned by:
Priority: normal Component: General
Version: 3.0.0.0 Keywords: occupancy
Cc: shorowit

Description

Requested here: http://beopt.nrel.gov/node/497

There isn't an obvious category to locate this in. Maybe Miscellaneous?

Change History (10)

comment:1 follow-up: Changed 3 years ago by ewilson

I would suggest an Occupants category under Miscellaneous and an Occupants Schedule category under Miscellaneous Schedules.

The Occupants category would have number of occupants as the sole input; 'auto' would use the HSP equation based on number of bedrooms.

We may want to change all of the HSP equation that use number of bedrooms to use number of occupants directly instead.

comment:2 in reply to: ↑ 1 Changed 3 years ago by shorowit

  • Version changed from Future to 2.5.0.0

Replying to ewilson:

We may want to change all of the HSP equation that use number of bedrooms to use number of occupants directly instead.

I am strongly in favor of this.

comment:3 Changed 3 years ago by ewilson

Scott, we had talked about the possibility of adding an input for occupants that would calculate an effective number of bedrooms to be used in occupant-related equations. It could have an auto option that uses the current behavior (number of occupants is a function of number of bedrooms).

This was a feature that came up on the FSEC ventilation controller call because they are interested in looking at an occupancy-sensor-based control. How difficult would it be to get this into 2.5?

comment:4 Changed 3 years ago by shorowit

  • Version changed from 2.6.0.0 to 2.5.0.0

comment:5 Changed 3 years ago by shorowit

Eric, can you provide the equation(s) that would be used?

comment:6 Changed 3 years ago by ewilson

If Nocc is a user input, use this equation to determine Nbr (both SF and MF):
Nbr = 1.6949*Nocc - 1.4746

For certain uses of Nbr we'll have to round to the nearest non-zero integer and cap at a max of 5 (e.g., hot water draws).

comment:7 Changed 3 years ago by shorowit

Just thinking this through... if a user specifies the number of occupants, it means that the # bedrooms input on the geometry screen will be meaningless, right? And I guess users will only be able to set a single value for multifamily buildings, if we are concerned about that.

comment:8 Changed 3 years ago by ewilson

Good points. I think we're okay with the # bedrooms input being meaningless, but it might not be obvious to users.

comment:9 Changed 3 years ago by ewilson

In multi-family mode, if 'auto' is selected for number of occupants, we will want to use the following equation to adjust the number of bedrooms to account for the increased occupant load in all the equations that use Nbr.

N_br,mod = (0.92*N_br - 0.24)/0.59

This is in addition to using the N_occ = 0.92*N_br + 0.63 equation for number of occupants as we are currently doing. We'll hav to round to the nearest non-zero integer and cap at a max of 5 for certain uses of N_br (e.g., hot water draws).

comment:10 Changed 3 years ago by shorowit

  • Version changed from 2.5.0.0 to 2.6.0.0

I don't think we should try to push this into the release.

Note: See TracTickets for help on using tickets.