I ended up coming up with a workaround myself: By extracting the wireframes of the triangles, culling only the variable-length sides, measuring their lengths, and converting those values to boolean (so that all the zero-length sides produce "false"), I was able to get a boolean collection to allow me to cull out the offending zero-area surfaces.
I was having trouble baking the pattern cull element — only when I attached a surface list to its output was I able to successfully bake. Not sure if that's a bug, but it is somewhat counterintuitive — when I /Andrew P.S. Why is it that, after a grasshopperbake command, if I use "Select last created" once, it gives me whatever I did before the bake, but if I do it TWICE, it correctly selects the baked elements? On Nov 16, 10:40 am, Andrew <[EMAIL PROTECTED]> wrote: > I have a grasshopper file that populates a surface with triangular > panels of varying sizes. Each triangular panel is generated by two > fixed points and a variable point, and when the variable point is at > the same place as one of the fixed points, its area is zero, but > grasshopper still generates a line-like surface. If I measure the area > of such a surface in Rhino, it comes out to be some infinitesimally > small number. I want to cull out all surfaces under a certain area > threshold, but any time one of these near-zero-area surfaces is fed > into the area component, the program crashes. > > Wanted to bring the problem to your attention and ask if anyone had > any suggestions for a workaround. Hope my description was clear enough > -- I can post an example file if necessary. > > Thanks! > > Andrew
