Change point order in nonuniform wacky grid

As you can see on this image, there is a line (points on it are created separately) in the bottom of the stack that is numbered nicely, and above it, there is a wacky grid, that is numbered in a weird fashion (no idea why, would like to hear the answer) that I want to learn how to control the order in such situations.

I want to use relative item component to triangulate the grid for structure visualization.

Feel free to alter and suggest easier ways for doing that, oh gods of grasshopper, cheers.

Attachments:

Glazing Structure.gh, 22 KB

Replies to This Discussion

Permalink Reply by David Rutten on November 2, 2015 at 3:52am

This roughly what you're looking for? I picked the edges directly off the surface via Rhino rather than extracting them from the Deconstruct Brep component. Either way works, I just prefer to pick the edge I want with the mouse rather than a slider.

Attachments:

Wall.3dm, 103 KB
GlazingStructure.gh, 13 KB

Permalink Reply by Tim on November 2, 2015 at 4:01am

Omg, the coolest grasshopper god!!!

Hey David,

Thank you for reply, I'll delve in immediately.

Did you notice the weird structure of the grid from the intersection component? It was structured like a fir branch, if you know what I mean. Could you explain why did that happen?

Permalink Reply by Pieter Segeren on November 2, 2015 at 4:13am

Ah PathMapper, I went with ShiftPaths :) Another highly rated component :)
I added a (w)hacky way to do this using the MultipleCurves(MCX) component: Edit: the Simplify on the Replace (R) input is superfluous~

Attachments:

GlazingStructure_PSG.gh, 32 KB

Permalink Reply by Tim on November 2, 2015 at 4:31am

This one is nice, the way I like it. I will try to arrange them vertically now to understand how it works (turns out I need them vertically anyway XD)

Thank you!

Permalink Reply by Pieter Segeren on November 2, 2015 at 4:41am

Just reverse the connecting order to the MultipleCurves component to get them vertically arranged :)

Notice I don't recommend this approach, using the CurveCurveIntersection component makes more sense.

Permalink Reply by Tim on November 2, 2015 at 5:04am

Ok, I'll try to go with CCI component now.

Btw, replace paths component worked with index A list directly, handy))

Edit:

Yeah, curve | curve intersection component works cleaner and creates a sequential grid of points later on, no wackiness, yey.

Thank you and Armin Seltz for the knowledgeable advices.

Permalink Reply by Pieter Segeren on November 2, 2015 at 5:16am

Ah - yes, of coarse ~:
Good catch!

If you decide to go the MCX-way, I would normally use AssignPaths from Human's Treefrog, but I somehow decided to make it with only native components this time - not sure why.

Permalink Reply by Tim on November 2, 2015 at 6:59am

Once again, hi and thanks for the help.

I looked into your definition, turn the grid in vertical order, when I realised that I needed to include the top and bottom rows as well, this is where I've met my nemesis. I'm not experienced enough to merge and edit nonuniform grids into something meaningful for relative item component for triangulation.

Here is an example of what I wanted to do but didn't know how:

Permalink Reply by Armin Seltz on November 2, 2015 at 3:57am

Ah, David beat me by 3 minutes.

The key is using the single curve | curve intersection component rather than the multi-curve one, because for that all the curves have to be flattened and you lose the tree structure for proper numbering.

Hope this helps too.

Attachments: