seed
seed copied to clipboard
BETTER -- BETTER HTML report shows N/A for results but SEED has values for
Describe the bug Some Property records, when a BETTER analysis is completed, have results in the SEED BETTER fields, such as Cost Savings, Energy Savings and GHG Savings, even though in the BETTER HTML report accessed from the SEED Analyses view, report N/A for those records.
Expected Behavior I would have thought if the BETTER HTML report says N/A, there would not be values in the SEED BETTER fields
Actual Behavior
- I perform a BETTER analysis on a set of records (origin is JCC, but anonymized)
- The BETTER HTML report shows N/A for savings
- The SEED BETTER fields have non-zero values
Steps to Reproduce
- Org: LBNL 404
- 10 properties and their meter data are imported from ESPM spreadsheet
- A BETTER analysis is performed on them as a portfolio
- viewing the report for "2550 Ninth Street" the building report shows N/A for results
- going to the Property List View, the BETTER results show values for cost, energy and GHG savings for that record
Instance Information
instance: dev1 SHA: 8101fa7d9 Org: LBNL 404 File: ESPM_BETTERTest.xlsx (derived and anonymized from JCC data) Link to file: https://docs.google.com/spreadsheets/d/1rr3rotrSglrJyXi4GZhvt46Jz5WetKB7/edit?usp=sharing&ouid=103887815394604824348&rtpof=true&sd=true
@RDmitchell I looked into this today, and it seems that perhaps this got fixed somewhere along the way? I tried it on my local with the ESPM_BETTERTest.xlsx file:
Let me know if you are still having this issue and I can look into it further. But it seems to have resolved itself
@kflemin -- It seems like dev1 is in a weird state right now, probably trying to wrap up this release, so I can't really test this.
I will try to get to it on Monday after the dust has settled.
@nllong review
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
I will retest soon on the current dev1 release
closing for release. Reopen if we discover that this is still an issue.