Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

GetSurfaceData errors and failure

I am trying to model a rather detailed 5-6 floor building that does not have symmetrical floors and thermal zones. I expected this to be a complex task for EnergyPlus and planned this steps: 1. Generate building model using OpenStudio 2. Interest and surface match. 3. Simple HVAC system matching zones and actual system 4. Calibrate in EnergyPlus

The model through me off with surface matching issues and intersection to which I manual surface matched each surface setting the boundary conditions (hoping I don't miss any surface).

During the trial run to check the integrity of the model, I get many GetSurfaceData errors like

** Warning ** GetSurfaceData: Interzone Surface Tilts do not match as expected.
**   ~~~   **   Tilt=0.0 in Surface=SURFACE 1084, Zone=THERMAL ZONE: SPACE 210
**   ~~~   **   Tilt=0.0 in Surface=SURFACE 1213, Zone=THERMAL ZONE: SPACE 7
** Warning ** GetSurfaceData: InterZone Surface Classes do not match as expected.
 **   ~~~   ** Surface="SURFACE 1084", surface class=Roof
**   ~~~   ** Adjacent Surface="SURFACE 1213", surface class=Roof
**   ~~~   ** Other errors/warnings may follow about these surfaces.

Is there a way to fix these issues without the need of investigating each surface in a text editor.

Some sever errors as I created new spaces after

** Severe  ** GetSurfaceData: Zone has no surfaces, Zone=THERMAL ZONE 22
** Severe  ** GetSurfaceData: Zone has no surfaces, Zone=THERMAL ZONE: 2-2
** Severe  ** GetSurfaceData: Zone has no surfaces, Zone=THERMAL ZONE: SPACE 1

GetSurfaceData errors and failure

I am trying to model a rather detailed 5-6 floor building that does not have symmetrical floors and thermal zones. I expected this to be a complex task for EnergyPlus and planned this steps: 1. Generate building model using OpenStudio 2. Interest and surface match. 3. Simple HVAC system matching zones and actual system 4. Calibrate in EnergyPlus

The model through me off with surface matching issues and intersection to which I manual surface matched each surface setting the boundary conditions (hoping I don't miss any surface).

During the trial run to check the integrity of the model, I get many GetSurfaceData errors like

** Warning ** GetSurfaceData: Interzone Surface Tilts do not match as expected.
**   ~~~   **   Tilt=0.0 in Surface=SURFACE 1084, Zone=THERMAL ZONE: SPACE 210
**   ~~~   **   Tilt=0.0 in Surface=SURFACE 1213, Zone=THERMAL ZONE: SPACE 7
** Warning ** GetSurfaceData: InterZone Surface Classes do not match as expected.
 **   ~~~   ** Surface="SURFACE 1084", surface class=Roof
**   ~~~   ** Adjacent Surface="SURFACE 1213", surface class=Roof
**   ~~~   ** Other errors/warnings may follow about these surfaces.

Is there a way to fix these issues without the need of investigating each surface in a text editor.

Some sever severe errors as I created new spaces after which I will remove one by one.

** Severe  ** GetSurfaceData: Zone has no surfaces, Zone=THERMAL ZONE 22
** Severe  ** GetSurfaceData: Zone has no surfaces, Zone=THERMAL ZONE: 2-2
** Severe  ** GetSurfaceData: Zone has no surfaces, Zone=THERMAL ZONE: SPACE 1

GetSurfaceData errors and failure

I am trying to model a rather detailed 5-6 floor building that does not have symmetrical floors and thermal zones. I expected this to be a complex task for EnergyPlus and planned this steps: 1. Generate building model using OpenStudio 2. Interest and surface match. 3. Simple HVAC system matching zones and actual system 4. Calibrate in EnergyPlus

The model through me off with surface matching issues and intersection to which I manual surface matched each surface setting the boundary conditions (hoping I don't miss any surface).

During the trial run to check the integrity of the model, I get many GetSurfaceData errors like

** Warning ** GetSurfaceData: Interzone Surface Tilts do not match as expected.
**   ~~~   **   Tilt=0.0 in Surface=SURFACE 1084, Zone=THERMAL ZONE: SPACE 210
**   ~~~   **   Tilt=0.0 in Surface=SURFACE 1213, Zone=THERMAL ZONE: SPACE 7
** Warning ** GetSurfaceData: InterZone Surface Classes do not match as expected.
 **   ~~~   ** Surface="SURFACE 1084", surface class=Roof
**   ~~~   ** Adjacent Surface="SURFACE 1213", surface class=Roof
**   ~~~   ** Other errors/warnings may follow about these surfaces.

Is there a way to fix these issues without the need of investigating each surface in a text editor.

Some severe errors as I created new spaces after which I will remove one by one.

** Severe  ** GetSurfaceData: Zone has no surfaces, Zone=THERMAL ZONE 22
** Severe  ** GetSurfaceData: Zone has no surfaces, Zone=THERMAL ZONE: 2-2
** Severe  ** GetSurfaceData: Zone has no surfaces, Zone=THERMAL ZONE: SPACE 1
editor.

GetSurfaceData errors and failure

I am trying to model a rather detailed 5-6 floor building that does not have symmetrical floors and thermal zones. I expected this to be a complex task for EnergyPlus and planned this steps: 1. Generate building model using OpenStudio 2. Interest and surface match. 3. Simple HVAC system matching zones and actual system 4. Calibrate in EnergyPlus

The model through me off with surface matching issues and intersection to which I manual surface matched each surface setting the boundary conditions (hoping I don't miss any surface).

During the trial run to check the integrity of the model, I get many GetSurfaceData errors like

** Warning ** GetSurfaceData: Interzone Surface Tilts do not match as expected.
**   ~~~   **   Tilt=0.0 in Surface=SURFACE 1084, Zone=THERMAL ZONE: SPACE 210
**   ~~~   **   Tilt=0.0 in Surface=SURFACE 1213, Zone=THERMAL ZONE: SPACE 7
** Warning ** GetSurfaceData: InterZone Surface Classes do not match as expected.
 **   ~~~   ** Surface="SURFACE 1084", surface class=Roof
**   ~~~   ** Adjacent Surface="SURFACE 1213", surface class=Roof
**   ~~~   ** Other errors/warnings may follow about these surfaces.

Is there a way to fix these issues without the need of investigating each surface in a text editor.