Thanks but I don’t consider myself an expert at Grasshopper. I’ve used it for nine years(?) and been active on this forum and its predecessor for eight years. I’ve read a lot of other peoples’ code, which is a great way to learn. I was a programmer in conventional languages for ~40+ years, with a penchant for detail (OCD?).
The code I posted here wasn’t perfect, though I fixed some things (below). I actually started with code from this post, not the reference I made earlier:
The current code is based on some observations of the dome geometry.
- There are 720 triangular surfaces.
- Disc and CullPt (white group) tells me that there are 362 unique points.
- These points are the centers of the hexagons and pentagons.
- So each of the 362 points has 5 or 6 nearby points around it.
I used Closest Points (‘N’ = 6, not 7) to get those nearby points but need a way to ignore one of them for the pentagons. I had used Smaller than 2 to cull them but that depends on model dimensions and would break if the dome were larger or smaller… So I’ve replaced Smaller with the purple group (below) to tell me if I should use only five or all six of the points.
The rest is details. Like sorting the 5 or 6 points AlongCrv (circles) to get them in proper sequence before connecting them with PLine, etc., etc.
Other facts I learned about the dome geometry:
- There are 362 “polygons” - no surprise, same as the number of unique points.
- Of those, there are 32 planar surfaces - 12 pentagons and 20 hexagons. All the rest are not planar.
geodesic dome_2023Feb25a.gh (44.2 KB)
P.S. I’m pleased and a little surprised that my sketchy purple group holds up when the ‘V Count’ slider value is reduced. Doing this breaks yesterday’s code.