Extract mesh faces that have naked edge/s?

Hi Everyone

Any thoughts on how i can extract mesh faces that have naked edge/s?

I currently have a computer heavy logic that uses face centres and closest points to reroute out the meshes i want but this does not seem like the best way.

Another idea i have been working on is using the naked mesh vertex index's to search all mesh faces to find which faces contain the naked vertices and use this data to extract them from the mesh, but yet to crack the logic to do this.

Thanks

Matt

▶ Reply to This

Replies to This Discussion

Permalink Reply by Andrew Heumann on February 5, 2012 at 10:56pm

Here's an approach that basically does what you describe, getting the indices of the naked mesh vertices and testing each face for the presence of one of those vertices. In the purple groups are two alternate ways of finding the naked vertex indices, one using the kangaroo naked vertices component, one using uto's "mesh edit tools". You might also be able to save a step at the end by using weaverbird's "Reroute Faces" component.

▶ Reply

Permalink Reply by Matt Gaydon on February 6, 2012 at 6:31am

Hi Andrew,

Thats a great help, although the logic of seaching with MIndex all faces does seem to be alot heavier than my closest point code logic i had written which i had not expected.

If i get anything super fast i will post it, as working with fractal meshes so the code gets heavy fast.

Thanks Again

Matt

▶ Reply

Permalink Reply by Andrew Heumann on February 6, 2012 at 8:35am

I've been thinking a little more... here's a faster way with some custom scripting. With the old version, a mesh with 10000 faces took 69.2 seconds, and the same mesh in the new version is figured out in under a second, and handles a mesh with 1,000,000 faces in under 20 seconds.

Attachments:

mesh_naked_face.gh, 6 KB

▶ Reply

Permalink Reply by Matt Gaydon on February 7, 2012 at 9:10am

Hi Andrew

Sorry for the Delay,

That seems super fast compared to the old system. I have realised though that i am better rethinking the overal logic of the system and build a less heavy mesh in place of subdividing down a large mesh then removing the excess at a later stage. Making the whole code faster lighter.

Thanks for all your help

Matt