search

kbenne / cbecc

Automatically exported from code.google.com/p/cbecc
0 stars 0 forks source link

CBECC Version 2013-2b (609) Unexpected Crash While Performing Analysis #653

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The current project I am working on is experiencing an unexpected crash during 
calculation. The CBECC program crashes without producing any helpful errors for 
the log file as well. The steps to reach the crash are pretty straight forward:

Step 1: Open the file.

Step 2: Click Perform Analysis button in toolbar.

Step 3: While performing analysis CBECC reaches 36% and crashes on “ab - 
Annual Translation(s)…”

When I open and perform the analysis the log file reads:

“2014-Jul-11 14:41:35 - Opening Project 'SanRoman\sanRamon4.cibd'...

2014-Jul-11 14:41:35 - Performing Building Database check...

2014-Jul-11 14:41:35 - Building Database check completed, no problems found.

2014-Jul-11 14:43:06 - Performing Building Database check...

2014-Jul-11 14:43:06 - Building Database check completed, no problems found.

2014-Jul-11 14:43:07 - Performing Building Database check...

2014-Jul-11 14:43:08 - Building Database check completed, no problems found.

2014-Jul-11 14:43:10 -   PerfAnal_CECNRes - Bypassing OpenStudio (and 
simulation) for zp model”

With no errors to go on I tried stripping down the project as much as possible 
to try and find the problem.  I started with deleting all the schedules and 
their references. The crash still occurred in this instance. Next I tried 
taking out all the spaces and creating only a simple geometry space, as a 
common cause of error is a space without six sides. The same crash occurred in 
this instance as well. I have attached the project itself as well as the 
stripped down version. Thank you.

Original issue reported on code.google.com by f.le...@gmail.com on 12 Jul 2014 at 12:45

GoogleCodeExporter commented 9 years ago

Original comment by f.le...@gmail.com on 12 Jul 2014 at 12:46

Attachments:

GoogleCodeExporter commented 9 years ago 
I attempted to run this model with v2b (installer version) and the progress box 
just faded, and I got a message the CBECC had stopped working.

Original comment by rhedr...@archenergy.com on 14 Jul 2014 at 8:50

GoogleCodeExporter commented 9 years ago 
I tried several version of this model and ran into CBECC-Com crashing and 
giving the same error as the user. One thing based on trial and error runs it 
appears that this maybe an issue with the Zone System (specially PTHP/FPFC - 
PTAC seemed to work fine). Also the error log from the crash indicates the 
crash on the openstudio_model.dll which might indicate some translation issue 
relating to the zone systems to OS. 

CCing David in case he has seen this happen on any model with Zone Systems

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name: CBECC-Com13.exe
  Application Version:  2.2.0.609
  Application Timestamp:    538df61e
  Fault Module Name:    openstudio_model.dll
  Fault Module Version: 0.0.0.0
  Fault Module Timestamp:   536ce927
  Exception Code:   c0000005
  Exception Offset: 0002387c
  OS Version:   6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1: 0a9e
  Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
  Additional Information 3: 0a9e
  Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Original comment by nka...@archenergy.com on 30 Jul 2014 at 5:07

GoogleCodeExporter commented 9 years ago 
Responded to user that we are currently investigating this issue and will send 
an update once we have resolution.

Original comment by nka...@archenergy.com on 30 Jul 2014 at 5:08

GoogleCodeExporter commented 9 years ago 
As Nikhil pointed out, the issue with this model is specifying ZnSys:Type = 
PTHP, even though the CoilHtg:Type = "HotWater".  Revising the systems to Type 
= PTAC mitigates the hard crash of CBECC when translating the ANNUAL models. I 
will add a CHECKSIM rule in v3 to warn users that PTHPs have to have 
CoilHtg:Type = "HeatPump"

Other issues:
- Invalid FluidSegs in 'Boiler Plant'
- 0 boiler capacity
- Mtr eff/MtrHP was too low
- Cooling/fan capacities for select ZnSystems are insufficient.

Attached is a model that runs through completion with v2b, but has remaining 
UMLHs.  Diffing the cibd with the original will clearly show the changes I 
made.  Assigning issue to Roger for review of the plant issues.

Also noteworthy; there is some suspect geometry in the file. Listed below is 
the relevant .err information; I did not dig into this further...

   ** Warning ** BuildingSurface:Detailed="SURFACE 21", underground Floor Perimeter = 123.22
   **   ~~~   ** ..which is less than its construction exposed perimeter.
   ** Warning ** GetSurfaceData: Very small surface area[7.07393E-004], Surface=SURFACE 134
   ** Warning ** GetSurfaceData: The total number of floors, walls, roofs and internal mass surfaces in Zone ZONE FOOD 303
   **   ~~~   ** is < 6. This may cause an inaccurate zone heat balance calculation.
   ** Warning ** GetSurfaceData: The total number of floors, walls, roofs and internal mass surfaces in Zone ZONE HALL/OFFICE 442
   **   ~~~   ** is < 6. This may cause an inaccurate zone heat balance calculation.
   ** Warning ** GetSurfaceData: There are 2 coincident/collinear vertices; These have been deleted unless the deletion would bring the number of surface sides < 3.
   **   ~~~   ** For explicit details on each problem surface, use Output:Diagnostics,DisplayExtraWarnings;
   ** Severe  ** GetSurfaceData: There are 1 degenerate surfaces; Degenerate surfaces are those with number of sides < 3.
   **   ~~~   ** These surfaces should be deleted.
   **   ~~~   ** For explicit details on each problem surface, use Output:Diagnostics,DisplayExtraWarnings;
   ** Warning ** ProcessSurfaceVertices: Possible non-planar surface:"SURFACE 116", Max "out of line"=1.74863E-004 at Vertex # 5
   ** Warning ** ProcessSurfaceVertices: Possible non-planar surface:"SURFACE 136", Max "out of line"=5.06605E-003 at Vertex # 3
   ** Warning ** DetermineShadowingCombinations: There are 2 surfaces which are receiving surfaces and are non-convex.
   **   ~~~   ** ...Shadowing values may be inaccurate. Check .shd report file for more surface shading details
   **   ~~~   ** ...Add Output:Diagnostics,DisplayExtraWarnings; to see individual warnings for each surface.
   ** Severe  ** DetermineShadowingCombinations: There are 2 surfaces which are casting surfaces and are non-convex.
   **   ~~~   ** ...Shadowing values may be inaccurate. Check .shd report file for more surface shading details
   **   ~~~   ** ...Add Output:Diagnostics,DisplayExtraWarnings; to see individual severes for each surface.

Original comment by da...@360-analytics.com on 30 Jul 2014 at 5:51

Attachments:

GoogleCodeExporter commented 9 years ago 
Can you add warnings on translation to SDD for:
1) Spaces with floor area of 0 or undefined
2) polyloops with area 0 or undefined
3) subsurfaces not contained within the parent surface
4) Surface with number of sides < 3
5) Spaces with total number of floor, wall, ceiling and roof surfaces < 6

Original comment by rhedr...@archenergy.com on 1 Aug 2014 at 5:34

GoogleCodeExporter commented 9 years ago

Original comment by rhedr...@archenergy.com on 1 Aug 2014 at 5:41

GoogleCodeExporter commented 9 years ago 
List above copied to issue 695.

Original comment by rhedr...@archenergy.com on 1 Aug 2014 at 5:46

GoogleCodeExporter commented 9 years ago 
The issue with this model that is causing the crash is specifying ZnSys:Type = 
PTHP, even though the CoilHtg:Type = "HotWater."  Revising the systems to Type 
= PTAC avoids the problem. We have added checks that will write out messages to 
warn users that PTHPs have to have CoilHtg:Type = "HeatPump."  Attached is a 
version of your file that fixes many of these issues.  

Your model also has other issues, including: Invalid fluid segments in 'Boiler 
Plant', boiler capacity of 0, motor eff/motor HP was too low, and cooling/fan 
capacities for select ZnSystems are insufficient.  There are also problems with 
the geometry, see the error messages below.

Original comment by rhedr...@archenergy.com on 3 Sep 2014 at 10:47