generative modeling for Rhino
Recently stumbled on this component while trying to work on a system for a facade on a studio project of mine. At this point, I'm running into some trouble with the feedback loops, as I'm basically trying to take a list of points on the border of a mesh piece, and search from each of those points one-by-one through a set of the equal number of subdivisions on the interior 'apertures' in the panel. With this logic, the edge of the triangulated mesh would be divided based on a set distance, and then the interior apertures would be divided equally based on their own lengths to match the number of divisions on the edge of the triangulated panel.
My problem seems to come in referencing the second part of the system, the searching of the closest points. I've been able to, using Hoopsnake 6.0.0 for the purpose of the prepended list feature, set up the original set so that it sorts through the edge mesh points one by one and sorts them into a list, but I can't seem to properly sequence the next portion in which each of those points would be used as a search point for a closest point node, which after the 'closest point' would be found, the list would then be culled to omit this point from the list of points to search.
If anyone can take a look at the script, I feel like it's a simple problem I just don't know quite what I'm doing wrong, or how to exactly sequence more than one of these hoopsnakes within eachother. Thanks for any help in advance, I'd really appreciate it as this is the last part of my studio project that needs to be finished!
This is a quick image from one of our presentation files which should help explain the system a little better.... The idea is to be able to take these pairs of points and use them with a weaving logic to expand the structural capability of the system, as well as connect the panels in a more interesting manner together
Not sure I understood correctly, but if you're trying to find closest points I'd say it's best to do without Hoopsnake, instead using the closest point(s) component and data trees. I'd suggest moving to that direction.