Not sure if i found an error in the code for the HB Deconstruct Object, but when I used the HB Faces by Attribute to sort out face types, it included the shades and aperture (see branch 0;1). Just wanted to share, as I’m guessing its not supposed to be this way, since the HB Deconstruct Object has dedicated outputs for those types of surfaces.
Hi @jakechevrier ,
I don’t fully understand why you would say this:
I can confirm that it is supposed to be that way since the Apertures and Shades are assigned to the Face objects. So, if you were to build a new room using those Faces, the Apertures and Shades would come along.
Do you have a specific question about “how to” do something? For example, do you want to remove the apertures and shades from the faces so that you only end up with geometries for Faces? If so, I can give some guidance on this.
That makes sense, I just misinterpreted the component… I saw the dedicated outputs for the child surfaces and was thinking it would work like this… Where the parent faces would come from the faces output, and the child surfaces would come from the child specific outputs.
This was sort of three-fold…
-
I was looking for a way to strip away the shading surfaces from the room (trying to solve my other recent post on “Stacked” HB Louver Shades)
-
Trying to determine a way to add wall thickness with minimal effort. We experimented with taking the extruded border shading surfaces and turning them into wall surfaces to match the reflectivity values of the wall.
-
I’m working with our lighting designers who like to use Climate Studio, so we’re attempting to construct a fluent shoebox workflow. We were looking to sort out all of the different surfaces by type and saw we had to “leave out” the (0;1) branch if using the method above. Now I realize the HB Visualize by Type component is the better approach, as we can separate the wall thickness (extruded border shades) from the exterior shades.
Definitely a nuanced case, but wanted to share. As always, appreciate the insight. thanks chris!
Good to know, @jakechevrier . We didn’t really expose a component to remove the assigned shading geometries but you can see under this section of the Honeybee Face SDK docs that there are several methods that will help you remove apertures, shades, etc. So you can always use those inside a custom GHPython component if you want to get rid of the shades or apertures assigned to a Face.