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

Hot water usage seems low #1236

Closed
jmaguire1 opened this issue May 1, 2024 · 4 comments · Fixed by #1265
Closed

Hot water usage seems low #1236

jmaguire1 opened this issue May 1, 2024 · 4 comments · Fixed by #1265
Assignees

Comments

@jmaguire1
Copy link
Contributor

jmaguire1 commented May 1, 2024

We recently made a change to hot water usage multiplier to try to get a more realistic spread in hot water usage (#1210), which gives much more reasonable variability but we're realizing had an unintended effect on the mean. The original distribution was 25% of homes had multipliers of 0.5, 25% of homes had a multiplier of 2.0, and the remaining 50% had a multiplier of 1.0, which led to an overall multiplier of 1.15. With the recent change, we have an average multiplier of 0.86 (see distribution below). The combined impact of this change is our average hot water usage decreased by 1.15/0.86 = 33% In a 30k sample run I did recently, we're seeing an average hot water usage of ~35 gal/day (after filtering out vacant units). I'm digging into good data sources for what national average number we should try to target, but my first inclination is we should be pretty close to the draw volume used for medium use water heaters in the UEF test (so 55 gal/day):

image

Thanks to Lixi and Rajendra for helping me figure this out and trying to work out the appropriate change here.

image

@jmaguire1 jmaguire1 self-assigned this May 1, 2024
@jmaguire1 jmaguire1 changed the title Hot water usage Hot water usage seems low May 1, 2024
@afontani
Copy link
Contributor

afontani commented Jun 23, 2024

The related PR for the data-driven multipliers: #1210. The PR provides a distribution fit to the multipliers. If the draws are low we have two options

  1. increase the number of events through the stochastic hot water draws
  2. increase the mean of the distribution of the multipliers.

If we increase the ~35 gal/day by 33% (the amount we reduced the multiplier was reduced), the increase will give us ~55 gal/day which you thought was reasonable. I am leaning toward the 2nd option and that we should update the multipliers again.

mean = 1.064 # An update from the original 0.8.
stdev = 0.2  # std dev of lognormal distribution is 20% (i.e. 95% CI is about 0.4-1.2)
u = np.log(mean**2 / (mean**2 + stdev**2)**0.5)
s = np.log(1 + stdev**2 / mean**2)**0.5
usage_multiplier = np.random.lognormal(u, s)

@jmaguire1 : Which option would you recommend? Are the number of events off or is the size of the draw off? In the PR above, we reduced the size of the draws.

@shorowit
Copy link
Contributor

shorowit commented Jun 24, 2024

We should coordinate/discuss this. We are looking to change the default OS-HPXML behavior for how hot water usage, as a function of number of occupants, is calculated, in which case you would ideally use multipliers with a weighted average of 1 in ResStock.

@jmaguire1
Copy link
Contributor Author

So I went back to the data from the field study and shifted it so we can keep a similar spread, but have a mean be 1.0 (basically option 2 Tony described):

Image

This is what the distribution of hot water usage multipliers would look like. Unless anyone objects to this approach, I think I'll update this in this manner. This also means that we'll be getting mean values consistent with what Scott is planning to change in terms of changing the default OS-HPXML behavior (to match this paper: https://www.fsec.ucf.edu/en/publications/pdf/fsec-pf-464-15.pdf)

@shorowit
Copy link
Contributor

shorowit commented Jul 3, 2024

Related PR: NREL/OpenStudio-HPXML#1761

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 a pull request may close this issue.

3 participants