Window blind difference in upgrade workflow?
@mdahlhausen is already working on this.
Since May 30, 2025.
Assessment
This issue has not been assessed yet.
Description
I don't have the whole picture right now, but here is what we know so far:
- The PV upgrade measure is showing small difference in end-use energy consumption. This measure does not impact building loads at all, since it is not a shading device. We expect no changes to HVAC or end use loads. This is one of the only measures we have where this is the case, so it might be revealing something new.
- I pulled a sample model. The model shows differences in sizing values (e.g. heat capacity, airflow, etc.).
- The IDF from the hardsize measure for both the baseline and upgrade workflow (before the upgrade measure is applied) show one notable change to window blinds. Both have blinds applied, but the applied windows are different in one case (see attached, and image below)
- A comparison of the OpenStudio output logs confirms that the applied blind area is different, despite both workflows using the same measure and code year (see attached, and image below).
- Overall, this has virtually no impact on stock results. But, it does show unexpected behavior when looking at distributional impacts.
Image compares IDFs from hardsizing measure for both workflow, with a difference in shading controls:
Image compares OpenStudio output logs, showing a difference in applied blind area between models. Note that this is before any upgrade measure is applied, suggesting a change in the baseline model construction between workflows.
Attachments:
ComStock simulation output logs
openstudio_output_up00.log.txt
openstudio_output_up41.log.txt
IDFs from hardsize measure
in_up00.idf.txt
in_up41.idf.txt
Final simulated OpenStudio models
in_up00.osm.txt
in_up41.os.txt
- Dominant language
- Ruby
- Stars
- 54
- Forks
- 28
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NatLabRockies/ComStock
-
Fresh comstockpostproc install fails on import: PyAthena 4.x requires SQLAlchemy 2 (AttributeError: sqlalchemy.types has no attribute DOUBLE)Possibly taken @JanghyunJK claimed this today. Openpostprocessing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NatLabRockies/ComStock#473 ·
-
Sampling broken with dependency changesMay be free again @asparke2 claimed this 93 days ago, and no pull request is open. Openbug
NatLabRockies/ComStock#462 · 1 assignee ·
-
Update S3 workgroup in gap model queriesMay be free again @eringold claimed this 270 days ago, and no pull request is open. Open
NatLabRockies/ComStock#453 · 1 assignee ·
-
postprocessing
Difficulty 3/5 1-2 days Newbie friendliness 35/100
NatLabRockies/ComStock#452 ·
-
Postprocessing setup and READMEs out of dateMay be free again @ChristopherCaradonna claimed this 275 days ago, and no pull request is open. Openpostprocessing
NatLabRockies/ComStock#451 · 1 assignee ·
All issues in NatLabRockies/ComStock
Similar issues
-
Visual COBOL: missing 11.0 and 12.0, and 9.0 date differs from Rocket Software's lifecycle pageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
endoflife-date/endoflife.date#11561 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
yegor256/netbout.rb#69 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yegor256/iccq.github.io#161 ·
Maintainers usually reply within 1 day