in the desired order.
0 = 0
1 = 1
2 = 6
3 = 7
4 = 8
5 = 9
6 = 12
7 = 13
8 = 2
9 = 3
10 = 4
11 = 5
12 = 10
13 = 11
Where the first number is the index and the second number is the actual sorting key. Then you sort these keys while sorting your curves in parallel using the A input of the Sort component.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
se the cull pattern, so I wanted to make the pattern using a function component. x=y. x= the original list and y= the interval i wanted to remove. So the pattern should be:
0: false
1:false
2:false
3:false
4:true
5:true
6:true
7:true
8:false
9:false
10:false
etc...…
Added by Rasmus Holst at 3:32am on November 17, 2009
ems in the same way. Lofting was particularly difficult, you had to have a separate loft component for every lofted surface that you wanted to generate because the component would/could only see one large list of inputs. Then came along the data structures in GH v0.6 which allowed for the segregation of multiple input sets.
If you go to Section 8: The Garden of Forking Paths of the Grasshopper Primer 2nd Edition you will find the image above describing the storing of data.
Here you will notice a similarity between the path {0;0;0;0}(N=6) and the pathmapper Mask {A;B;C;D}(i). A is a placeholder for all of the first Branch structures (in this case just 0). B is a place holder for all the second branch structures possibly either 0, 1 or 2 in this case. And so forth.
(i) is a place holder for the index of N. If you think of it like a for loop the i plays the same role. For the example {A;B;C;D}(i) --> {i\3}
{0;0;0;0}(0) --> {0\3} = {0}
{0;0;0;0}(1) --> {1\3} = {0}
{0;0;0;0}(2) --> {2\3} = {0}
{0;0;0;0}(3) --> {3\3} = {1}
{0;0;0;0}(4) --> {4\3} = {1}
{0;0;0;0}(5) --> {5\3} = {1}
{0;0;0;1}(0) --> {0\3} = {0}
{0;0;0;1}(1) --> {1\3} = {0}
{0;0;0;1}(2) --> {2\3} = {0}
{0;0;0;1}(3) --> {3\3} = {1}
{0;0;0;1}(4) --> {4\3} = {1}
{0;0;0;1}(5) --> {5\3} = {1}
{0;0;0;1}(6) --> {6\3} = {2}
{0;0;0;1}(7) --> {7\3} = {2}
{0;0;0;1}(8) --> {8\3} = {2}
...
{0;2;1;1}(8) --> {8\3} = {2}
I'm not entirely sure why you want to do this particular exercise but it goes some way towards describing the process.
The reason for the tidy up: every time the data stream passes through a component that influences the path structure it adds a branch. This can get very unwieldy if you let it go to far. some times I've ended up with structures like {0;0;1;0;0;0;3;0;0;0;14}(N=1) and by remapping the structure to {A;B;C} you get {0;0;1}(N=15) and is much neater to deal with.
If you ever need to see what the structure is there is a component called Param Viewer on the first Tab Param>Special Icon is a tree. It has two modes text and visual double click to switch between the two.
Have a look at this example of three scenarios in three situations to see how the data structure changes depending on what components are doing.
…
4, 3, 7, 7, 7, 8
would need to be
5, 6, 7, 8, 4, 3, 7, 8
ideas?
current workaround (kangaroo dupPt component) removes all duplicates from list, tho does maintain order.
thx…
ow do you sort data trees with distinctive number of list items in each branch?
In this example, there are 161 branches with three distinctive number of list items, 3, 4, and 5. I want to know if there is another way to sort out this data tree into this way: 3 vertices {0;0}, {0;1}, {0;2],...4 vertices {1;0}, {1;1}, {1;2},... 5 vertices {2;0}, {2;1}, {2;2},...
2. Is there a way to sort our surfaces based on number of distinctive list items automatically? For example, if there are surfaces with 3, 4, 5, 6, and 7 vertices, I want to make five branches with the same number of vertices automatically.
I hope my questions make sense...
Thank you!
Dongyeop …
Added by Dongyeop Lee at 12:14pm on October 3, 2016