SWBE016-01 Efficient Sliding Glass Doors, Storefront - New Measure

[SJeffery97]

SWBE016-01 Efficient Sliding Glass Doors, Storefront

Energy modeling: Debrudra Mitra @Debrudra20
Postprocessing: Debrudra Mitra @Debrudra20

Measure Summary:
This measure is for installing efficient glass sliding entry/exit doors to reduce heat loss or gain through the door.
For grocery prototype, the geometry.pxt was changed to add a representative exterior door to the prototype and the zonetemplate.pxt was changed to simulate air leakage from the newly added glass door. The root.pxt for grocery was changed to include air leakage and thermal properties parameters.

Measure list: DEER_EnergyPlus_Modelkit_Measure_list_EffDoors.xlsx

Energy Consumption: meas_impacts_2024_com.xlsx

PR Author

• Make sure the PR branch is up to date with main branch at the time of the PR submission
• Craft a succinct title that effectively encapsulates the essence of the pull request, providing a general overview of the proposed changes.
• Label the PR with at least one of the following: New Measure, Bug, or Feature.
• Provide a concise description of the measure, bug, or feature. Submit one PR per measure.
• For a new measure, attach a workbook named DEER_EnergyPlus_Modelkit_Measure_list_working.xlsx, containing only rows used for post-processing the measure.
• Add comments in the code when necessary to facilitate the review process.
• Add a comment before the added code, including the author's full name, company, and specifying if it's a bug fix, new measure, or feature.
• For a new feature or bug, demonstrate the impact on energy consumption for selected cases with justification using plots and descriptions.
• For a new measure, add a summary table showing total energy consumption per simulated case.

PR Reviewer

• Conduct a thorough code review.
• If the branch is behind the main, merge the branch locally to check for potential conflicts.
• If a bug, locally reproduce it and compare energy consumptions before and after.
• Explore creative ways to stress-test the code.
• Locally check the error file and other outputs.