[solved] split building mass component works for only a few masses

in the attached demo file, the split building mass component only processed a few of the masses for the lower floors of the building.

May I ask what is causing the problem?

Thank you!

Attachments:

typology_v003.gh, 476 KB

Replies are closed for this discussion.

Replies to This Discussion

Permalink Reply by Grasshope on January 14, 2016 at 10:19am

it seems the workflow only works for the first 9 massing ....

Appreciate if you can kindly advise!

Attachments:

typology_v006.gh, 487 KB

Permalink Reply by Antonello Di Nunzio on January 14, 2016 at 12:25pm

Hi Grasshope,

I have analyzed your file, for some wierd reason, Honeybee's component cannot read 4 breps correctly as can you see on the image below. And they cause problems.

I have modified and simplified your script using cap function and now it works fine.

You could make a script that changes height of section planes inside a range so the height of floors change, too.

Bests

Antonello

Attachments:

typology_v003_mod.gh, 517 KB

Permalink Reply by Grasshope on January 14, 2016 at 9:15pm

Noted with many many thanks, Antonello!

I learn a lot from your suggestions!

I'll try to test the model for E+ simulation.

Permalink Reply by Mostapha Sadeghipour Roudsari on January 14, 2016 at 11:56pm

Thanks Grasshope and Antonello. I think we should log this as a bug or as an enhancement request on github.

Permalink Reply by Chris Mackey on January 31, 2016 at 7:30pm

Hello Everyone,

Sorry for being so late here. I have put in a bit of code to stop the component from failing and you can find this in the attached file.

Still, I wish I could make this component work in all cases but, as I mentioned in the tutorial video, it is not going to be possible to make a component that will work for all cases (there were just too many bugs in Rhinocommon that came to the surface when I was writing this one).

One thought that I have had is to separate this component into one that splits masses into floors, which I know can be written to never fail, and another that splits flors into core/perimeter, which won't work in all cases but I can get better control over the failures this way.

Let me know if this will be helpful and I will add it to the github issues.

-Chris

Attachments: