kbenne / cbecc

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

CBECC-Com Issue - Unexpected Crash #889

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Version = 2013_3a_687

Category = Unexpected Crash 

Hi, whenever I try to assign the visible transmittance property to a window 
construction in my file and then run the program it causes CBECC-com to crash. 
I can’t figure out if something is wrong with my windows or if there is a 
memory limitation to daylighting simulations as this is a very large project. I 
am aware of the other issues with incomplete HVAC systems, but still can’t 
figure out why if I add VT to a window construction and run the simulation it 
crashes. Moreover, when I try to add another window construction it also seems 
to crash. Also, if I edit anything in the text version of the cibd file it also 
seems to crash when I reload it. Is there a certain encoding format I need to 
save it in?

Original issue reported on code.google.com by f.le...@gmail.com on 23 Dec 2014 at 8:34

GoogleCodeExporter commented 9 years ago
Transferring ownership to Luke. 

Original comment by rhedr...@archenergy.com on 30 Dec 2014 at 7:32

GoogleCodeExporter commented 9 years ago
Roger - 

It appears there may be an issue with the DaylightableArea ruleset function 
which calculates daylit areas.  When the software crashes, the last rule 
evaluated is typically the DaylightableArea function for one of the spaces on 
level 5.  

I don't have the ability to debug this function, as it resides in source code. 
I am going to transfer ownership of this issue to Scott.

Original comment by lu...@360-analytics.com on 30 Dec 2014 at 10:38

GoogleCodeExporter commented 9 years ago
The problem here traces back to Space geometry.  The PolyLp that describes the 
boundary of the Spc 'S-L05MEEL17 MEEL' contains two slivers, which in turn 
causes the daylit area calculations to crash the program.  The diagram attached 
below shows the problematic vertices.
A copy of the building model that includes a fix to this PolyLp will be 
forwarded to the user reporting this issue.
Also attached to this issue is a copy of the log messages describing analysis 
errors (following entry of missing FenCons data).

Leaving this issue open until fix added to compliance manager to resolve 
slivers like this during normal model defaulting.

Original comment by scriswel...@gmail.com on 11 Feb 2015 at 12:27

Attachments: