Cull/Delete faces in mesh in Topography mesh

Replies to This Discussion

Permalink Reply by peter fotiadis on January 8, 2016 at 11:47am

Well ...

... for a mesh massacre based on slope (mesh face normals) see attached. I'll add later various other ways (points et all) to kill properly a mesh.

NOTE: Daniel's MeshMachine is used in order to control the demo mesh "density" (but you can provide any mesh in fact).

BTW: do you want a small C# that reduces a mesh?

Attachments:

• massacre_due_to_slope_V1.3dm, 268 KB
• massacre_due_to_slope_V1.gh, 16 KB

Permalink Reply by Daniel Domenech Muñoz on January 8, 2016 at 1:15pm

Guaaau, that's great. The killing was in order. Now its populations of faces is 30000, 9000 less. 

Ok, i have installed Plankton, it seems and interesting add-on

How it is that C# maybe it is interesting?

P.S: Massacre at Mesh Fall, is not the titel of the new Fargo Season?

Attachments:

• 12510706_10208523937642592_2117241705_o.jpg, 121 KB
• 12516773_10208523879521139_772555001_o.jpg, 124 KB

Permalink Reply by peter fotiadis on January 8, 2016 at 11:59pm

Hmm ... appears that you have a "solid" as a mesh not just a "surface" (the "vertical" parts) - that said I confess that I never exploited your file (30K faces makes me nervous, he he).

Anyway get the massacre MK2 (reduce mesh)  C# that maybe has more sense in your case.

The very same test surface is used (Load R file first): notice the PlanA (reduce) and PlanB (MeshMachine).

Moral: massacre (kill first then ask questions)

Attachments:

• Mesh_check_and_reduce_V2.gh, 159 KB
• Mesh_check_and_reduce_V2.3dm, 143 KB

Permalink Reply by peter fotiadis on January 9, 2016 at 1:09am

Added another massacre option (maybe not suitable for this case ... but since I hate meshes killing some is always a pleasure, he he).

Note: same test brep is used as in the first massacre def

Attachments:

• massacre_due_to_slope_or_ratio_V1.gh, 128 KB

Permalink Reply by Daniel Domenech Muñoz on January 9, 2016 at 1:47pm

I'm agree, it is a pleasure to kill mesh

Very useful tools, thank you for your time Lord Fotiadis

Permalink Reply by Chris Hanley on January 8, 2016 at 1:55pm

NOTE: the attached sample definition can take a few seconds to compute with the provided mesh.

Here are some steps that use native GH components.  The description is a bit lengthy...sorry.  I got carried away on lunch break...

1 - Clean up the mesh a bit:  Lots of ways to do this, but as a rule of thumb, it's probably best to clean the mesh as best you can before bringing into GH.  But, for the sake of example...a basic method is comparing the normal of a face to a Z Vector, and if the comparison results in a match, within some tolerance...then you can get rid of it.  When dealing with topography and slope, the common unit of measure is generally percent, but to start with, we can use degrees.

2 - Evaluate MeshFaceNormals: similar to step 1, you are simply getting the normal vector of a face, and comparing it to a Z vector.  The important thing to note is that the Vector Compare component outputs radians.  At this point, you need to either convert to degrees again, OR, do some math and convert to percent.  

3 - Set Slope Zones and Ranges : There are a few ways to do this, but I think this is one of the most straight forward methods.  Set your "slope zones", create some consecutive domains from those numbers, then just find the values that fit into those domains, (you have the values from step 2, so you can pump those into the N input of the Find Domain component.)

4 - Color Mesh by Slope Value : the gradient component is setting colors based on your slope range domains.  Because you have input a list of domains, (0 to 10, 10 to 20 , 20 to 25, 25 to 40, and 40 to 60), the Find Domain component is actually just putting the slope values into the corresponding range, and then outputting the index number of the slope domain, (0,1,2,3,4).  The gradient component then maps those 5 numbers, (0-4.....which is actually 5 numbers because list counts start, and include, 0), to 5 colors.

4a - NOTE: The gradient component needs a Lower limit, and Upper Limit.  In this case we start the lower limit at 0, (index of first slope range...0 to 10).  The upper limit is the index of the LAST item in the Slope Zone/Range list, which is 4.  I used a list length component to get the length of the below list, (which correctly returns 5 items....but I need the index of the last one, so the expression subtracts 1 from the length total).

0. 0.0 To 10.0
1. 10.0 To 20.0
2. 20.0 To 25.0
3. 25.0 To 40.0
4. 40.0 To 60.0

Then construct the mesh again using the cleaned vertices and faces from step 2, only adding in the new colors.

The last bit of the definition is just visualizing the slope value on the face...it's kind of overkill, but shown as an example.

Attachments:

• MeshCleanAndSlope.gh, 19 KB
• MeshCleanAndSlope.3dm, 2.8 MB

Permalink Reply by Daniel Domenech Muñoz on January 9, 2016 at 1:44pm

Thank you   This is really nice and work perfectly! Thank for your time, Chris