Honeybee | Honeybee_Intersect Masses is removing the centroid of my geometries

I am trying to simulate a building which has 4 office towers, three spaces which connect the towers, southern and eastern corridors/egress, and a podium which the aforementioned massing sits upon. I have created each of these as a separate piece of geometry and each can be independently run through EnergyPlus, however my intent is to run all of them as a whole building. I have not been able to do this yet due to the fact that when I intersect the separate masses to ensure that the surfaces are divided properly I am unable to proceed in the simulation workflow because I am getting a "Solution Exception: NoneType object has no attribute 'Centroid'" error.

What could I be doing wrong such that I am getting this error? I have attached my files for reference.

Thanks for the help, I really appreciate it.

Attachments:

Ennead Staten Island Courthouse.3dm, 461 KB
Experiement - Staten Island Courthouse.gh, 217 KB

Replies are closed for this discussion.

Replies to This Discussion

Permalink Reply by Chris Mackey on November 1, 2014 at 7:26pm

Hi Nicholas,

Thank you for posting. I will be perfectly honest and say that the geometric acrobatics that go on to split masses into core and perimeter and then intersect these geometries to make reciprocal surfaces is fraught with bugs, many of which are not just the result of LB+HB code but are also issues that are being worked through by McNeel and the creators of RhinoCommon.

Volumetric operations like this are just a really tough thing to automate when you have the complex geometric capabilities that Rhino gives you to start with. In the process of making components to do split up these volumes, I have discovered a fairly long list of things that are at least idiosyncrasies in RhinoCommon if not unintentional bugs. I am going to post these all to Guilio at some point soon but I have developed a few workarounds in the interim.

Notably, I just loaded a few more into the Intersect masses component after looking deeper at your issue and it should now be able to handle core and perimeter zones and not fail (though I still recommend baking/checking the output geometry). In any case, your primary problem was resulting from the fact that you put intersected geometry into the splitBldgMasses component and this is not recommended. You usually want to use the intersectMasses component after you have split your building up into zones. I have since put in a warning to make users aware of this if they do input intersected geometry.

So the general guidelines for using these components are as follows:

I have attached a GH file that shows you these results with your building geometry. Let me know if you encounter any other things that seem like big bugs as you assemble the zones for the rest of your building.

And a happy Day of the Dead!

-Chris

Permalink Reply by Chris Mackey on November 1, 2014 at 7:36pm

Woops. Forgot to attach the right GH file

Attachments:

ExperiementStatenIslandCourthouse_CWM2.gh, 274 KB

Permalink Reply by Andressa L. Saraiva on July 18, 2016 at 12:40pm

Hello Chris, I have a similar problem, except that I am not using the Intersect Masses component. My definition was working perctly well in the beggining, but when I add the Split Building Mass component, the simulation stops working. What can I do to solve this problem?

I started a discussion here in the page:

http://www.grasshopper3d.com/group/ladybug/forum/topics/split-build...

Permalink Reply by Nicholas Rekstad on November 3, 2014 at 7:12am