Grasshopper

algorithmic modeling for Rhino

Problem when using the index output of 3D Proximity to create a mesh

I am trying to use the index integers from the 3D Proximity Component to create mesh faces.  When I define the mesh faces with the given indexes, the algorithm structure I a using seems to be creating at least one face per set of three points.  I am want exactly one face per set of three points.  

 

I have attached a demonstration of what I'm talking about.  I use a few weaverbird components to show the problem clearly

 

I can think of two ways of solving this:

1. Find a way of defining the mesh faces which does not cause redundancies.

2. Delete redundant face definitions

a. i can check for redundancies in the sets of index integers used to define faces.  This could be easiest in that i would be comparing sets of numbers

b. i can check for redundancies in the set of face representations of the output. 

 

Any suggestions would be great. Thanks!!

 

Best 

--

Kero

Views: 471

Attachments:

Replies to This Discussion

Nevermind.  The shear amount of faces created was throwing me off but they actually are all unique.

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service