Glazing - rhino crash

Hello guys and girls,

I am getting really god at crashing rhino lately. So I am asking you for a little bit of help. I am doing a test to see if the location of different zones affects the energy outcome (thesis project) but when I put just the second level in - approx a total of 80 zones in total - it crashes when it should calculate the glazing. However it does it for the first 40 zones (first level) but not when I add the second level. So I am really puzzled to why is that - are there any settings I am skipping?

Any crazy ideas are more than welcomed! I have added the definition for who wants to take a peak. ;)

Attachments:

29-03-2016.gh, 1.8 MB

Replies are closed for this discussion.

Replies to This Discussion

Permalink Reply by Mingbo Peng on March 29, 2016 at 6:50am

Hi Stefania,

I have no problem with adding glazing first before solve adjacency.

-Mingbo

Attachments:

29032016_edit.gh, 1.8 MB

Permalink Reply by Stefania Dinea on March 29, 2016 at 6:59am

smart! thank you so much - it never occurred to me to do it in reverse.

Permalink Reply by Stefania Dinea on March 29, 2016 at 9:08am

spoke to soon, have the same issue no matter how I turn and twist stuff.

Permalink Reply by Mostapha Sadeghipour Roudsari on March 29, 2016 at 1:02pm

Hi Stefina. Is your Rhino updated to the latest version?

Permalink Reply by Stefania Dinea on March 29, 2016 at 1:09pm

Yes it is. I reinstalled windows this weekend and reinstalled Rhino, the latest edition.

Permalink Reply by Stefania Dinea on March 29, 2016 at 9:11am

BTW .. your method adds windows on the inner walls ...

Permalink Reply by Chris Mackey on March 30, 2016 at 8:08pm

Hi Stefania,

You are indeed becoming an expert at crashing Rhino. Again, this is happening for the same reason as your previous post (http://www.grasshopper3d.com/group/ladybug/forum/topics/glazing-cre...), which is that Rhino is getting overwhelmed by the "guess and test" method that is used to find the correct offset distance to make the window from the edge of the wall surface. Rhino really does not like these "while" loops for "guess and check" functions and there is really nothing that I can do to completely solve it as it's an issue on McNeel's end.

However, in the event that this helps the component be more robust, I just re-wrote the guess-and-check function to use this awesome fast method that I pulled from the CBE comfort tool. At the least, I can tell you that the component is now faster than it was before:

Hopefully, this means that it will also be able to handle more of the curved geometry that you throw at it before Rhino crashes.

Also, I should say that this guess-and-check method is only used for curved surfaces so the easiest way to solve your problem (and make the component run faster) is to planarize your geometry.

-Chris

Attachments: