NREL / EnergyPlus

EnergyPlus™ is a whole building energy simulation program that engineers, architects, and researchers use to model both energy consumption and water use in buildings.
https://energyplus.net
Other
1.12k stars 389 forks source link

Kiva geometry convention/s #10522

Open Tokarzewski opened 4 months ago

Tokarzewski commented 4 months ago

Description There is a discrepancy in how DesignBuilder, EnergyPlus and Kiva handle geometry conventions, leading to mismatches when integrating Kiva objects. This issue was identified while using DesignBuilder to create EnergyPlus simulations. The defect manifests when Kiva's only inner geometry convention conflicts with other geometry conventions (e.g., outer or center-line) used in the DesignBuilder. A long-term solution could involve allowing Kiva to recognize different geometry conventions.

"The foundation shape is defined by the description of a single polygon. The perimeter of this polygon defines the location of the interior surface of the foundation wall." KIVA docs (not EP KIVA)

image

image

Example consider a shoebox model: in both inner and outer geometry conventions, the exposed perimeter fraction should be 1, but the area will differ as walls have thicknesses, meaning the 2D Kiva geometry model should also differ, but because Kiva requires inner geometry, we should not provide floor surface with external dimensions.

Details Platform: All supported platforms Version of EnergyPlus: Identified in EP 23.1 Helpdesk ticket number: #16567

SuppFiles.zip

jmarrec commented 3 months ago

This seems like something that should be reported to design builder or to Kiva, maybe I'm missing something.

Tokarzewski commented 3 months ago

Hi @jmarrec

To clarify, DesignBuilder does not utilize Kiva as a standalone engine. Instead, DesignBuilder uses the EnergyPlus implementation of Kiva through the use of Foundation:Kiva:Settings and Foundation:Kiva objects.

I am from DesignBuilder support and I already discussed this issue through the EnergyPlus support desk #16567. I was advised to submit this as a potential new feature request through the Github issues platform.