I'm sticking with Equilateral triangles for this project, any 'half-size' triangles that make up the edge of the grid will be resolved as 'adaptive components'. If it can be avoided, great, if not, that's cool. Essentially, I know what I want to do but don't the components well enough to model it in Grasshopper…

With that said, here is what I'm attempting to do with this TriGrid…

1. Control the total number of equilateral triangles that will compose/fill a rectangle of defined area. Right now I only have an integer value for number of triangles in the X and Y direction (I don't know how in Grasshopper to even define the area of the rectangle yet (read: my building facade) - but I know what dimensions I want for it, which will need to flex/change so that I can solve for multiple facade areas). So, I'm assuming that one would start with how to define the rectangle/bounding area itself and fill it using the TriGrid component which would be defined/divided up somehow to control each triangle individually.

So, for example, let's say I had a 100' x 75' rectangle and wanted to divide it into only 25 equilateral triangles, but the triangle edges could be of any integer lengths between 1 and 10 so that you wouldn't have this even grid of triangles but a 'random' collection of triangle sizes. Then, run Galapagos and see what the solutions look like and again for multiple 'numbers' of triangles (25, 50, 100, etc)

2. Take the problem above and now suppose that you give priority to only one side of the rectangle and define that only triangles of sizes 5 through 10 can touch that priority edge.

Run this for multiple 'numbers' (sets?) of triangles (25, 50, 100, etc).

3. Take the problem above and define that one triangle of each length 1 through 10 must touch the priority edge. Once again, run this for multiple sets of triangles (25, 50, 100, etc). It would be great to mix this up and say that two triangles of length 5 must touch the edge and four triangles of length 8 must touch the edge, etc.

4. Same idea as above, but add another layer/(fitness?) to those iterations that have the largest (or smallest) triangle at the midpoint (or maybe endpoints) of that priority edge.

5. If I can get to there, I'd like to model four sides concurrently, so that the edge condition between two faces is now the priority. In other words, say that one face is modeled for question #2 (of the above questions) and the other face is modeled for question #4 and the fittest version is the one that has the fewest (or most) triangles on that particular edge condition. I'm content to Bake/Photoshop these 2d rectangles together to make up these scenarios as it might just prove too processor heavy to combine everything into one model. But I think that's the final project right there.

If anyone can spell out just in a sort of (use this component) > (do this/use this component) > (etc) for me I would be really grateful. Thoughts?