Strange wall geometry Honeybee

Hello,

I’ve encountered some unusual wall geometries even tough the window geometries looks correct. I’ve set the file in meters with a tolerance of 0.01, checked if the windows were coplanar with the zone, and offset the windows form the zones borders.

I’m unsure if this is a bug or if I’ve made a mistake that I can’t identify. I’ve attached the Grasshopper definition here.

Any assistance would be greatly appreciated.

Thank you.

strange aperture.gh (283.7 KB)

tolerance

Hi @tru, it looks like you may have missed internalizing the apertures in the grasshopper script.


best
-trevor

Hi @TrevorFedyna

You’re absolutely correct. My apologies for the oversight.
Here’s the updated version of the previous file.

strange aperture.gh (382.0 KB)

Hi @tru, thanks for uploading another file.
the model validates and seems to have no issue when put into openstudio, there appears to be no issue

also baking the model with the pollination rhino tool and it shows no issue in the geometry as well
image

I think that what you are experiencing might be a visual bug in how the model is being displayed, because everything else is looking good, but I could be wrong
-trevor

1 Like

Hi @TrevorFedyna

Thank you very much for the feedback.
I’m glad to hear that it’s working for you.

Initially, I thought it might be a visual glitch, but I’m puzzled as to why I’m encountering the same unusual geometry even when I bake it from another laptop.

Have you attempted to bake the geometry from Rhino Grasshopper as well?

@tru

Yes I’ve seen this before as well. It appears to happen most commonly when I have apertures that are touching one another (mulled windows), or apertures that are touching the edge of a face.

The simple fix I use most often is to just scale all the aperture geometry by 0.999 - this will make it so they are not ‘touching’ one another, but does not affect their size so much that it affects the simulation results. Its a hack to be sure, but it usually seems to work ok.

Of course, you could also manually re-size each window by 1mm or something to gap them, that would also work in most cases.

best of luck with it
@edpmay

3 Likes

Hi @edpmay

Thank you so much for the suggestion, it finally worked for me too.
The problem was that there were some apertures touching each other.

Thanks to both of you for your assistance.

2 Likes

I just wanted to say thank you, @edpmay and @TrevorFedyna for answering this.

Ed’s explanation is correct that Rhino just struggles to display these cases of Apertures touching one another. But we consider these cases valid and they will simulate correctly in any of the engines (E+, Radiance, etc.).

FYI, @edpmay , an alternative to your solution here:

… is to just offset the Apertures using the new “HB Offset Aperture Edges” component. You can specify an offset distance here that is equal to the model tolerance and this should always get the windows to display nicely in Rhino with the smallest change in overall Aperture area. More info on this new component (along with some other use cases) can be found in this thread on the Pollination Forum:

Offset_Aperture_Component

3 Likes

Hey @chris ,

I just went to use the new offset tool here, but is it correct that it cannot work on the apertures themselves - it only works on the whole room once the apertures are already added to it?

It would be great if it could operate on the apertures ‘before’ they get hosted - that way we could use it to solve a handful of common hosting issues (apertures on the edge of a room geom, etc…).

Is there some reason that the apertures need to be hosted first though before this can work properly?

Thanks @edpmay ,

Well, the repair_ option will be a little meaningless when the apertures are not hosted since we don’t know if they’re extending past their parent Face if there’s no parent face yet.

And I guess I was figuring that, if all you want to do is offset the aperture geometry, you can do this more easily with a native grasshopper Offset component before you create the Aperture rather than using a Ladybug Tools component.

Can you be more specific about why you might want this particular component to work with the aperture objects?