Window blind difference in upgrade workflow?

Aperta
  • Qualcosa non va?
#355 0 commenti 0 reazioni 2 assegnatari Vedi su GitHub

@mdahlhausen ci sta già lavorando.

Dal 30/5/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

bug

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

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.
Image

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

Lingua principale
Ruby
Stelle
54
Fork
28
Merge medio
3g 23h
PR unite (30g)
5

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di NatLabRockies/ComStock

Tutte le issue di NatLabRockies/ComStock

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.