{0;1;0}N=6
{0;1;1}N=6
{0;1;2}N=5
{0;2;0}N=7
{0;2;1}N=8
{0;2;2}N=9
Can you shift and wrap any of the paths A B or C?
Say if I wanted to shift and wrap B by 1 to get the following...
{0;0;0}N=7
{0;0;1}N=8
{0;0;2}N=9
{0;1;0}N=3
{0;1;1}N=2
{0;1;2}N=5
{0;2;0}N=6
{0;2;1}N=6
{0;2;2}N=5…
p them in two different group of points, but mantaining their structure, because first I need to move them in different ways and later group them again to create lines between them:
0. null 0. a
1. b 1. null
2. c 2. null
3. null 3. d
4. null 4. e
5. f 5. null
Thank you
…
3} N=2
....
{527} N=4
What I want to do is figure out the same the item in group A and retrieve their branch index so that I can get the corresponding item in group A. Is there any way to make it?…
shift. I realize I can use 'replace branch' but I do not have an available mask to utilize. I have simplified the problem to its simplest form so my question is understandable, however, the tree I am trying perform this operation on is a much larger 3 digit path address.
{1;3;2}
{2;3;4}
{3;5;4}
{4;3;7}
Change the above list to the list below.
{0;3;2}
{1;3;4}
{2;5:4}
{3;3;7}
I wish for a more robust arsenal of branch manipulation components. Most of the things I need to do are possible with the existing components, however, many operations take several components to perform even simple manipulations. Since branch/path manipulation is so integral to using GH successfully, it seems the GH community would be well served by enhancing the available path manipulation components.
Thanks,
Stan
…
would like to group the paths based on their item count (n) values resulting in a tree which should look something like this:
{0;0} (3)
{0;1} (2)
{0;2} (2)
{0;3} (1)
in other words, all paths with 2 items are under one path, all with 6 items in another, and so on.
I feel that the pathmapper should be able to do this very easily but cannot figure out what the expression should be... I have tried searching the forum but have not had much luck!
Any ideas? Thanks a ton!…
ow should the new curve be? Should it have a Z=3, a Z=2, a Z=5(2+3) or a startZ=3 and endZ=2?
There would also be a problem if 2 curves intersect somewhere in between their endpoints... How should this point's movement affect the curves?
Maybe you should rethink your approach. If your end goal is to move the curves maybe it would be more efficient to get the endpoints of each curve instead of the intersection points...
Take a look at the attached example file. Can you draw in rhino the final curves (after move)? It would help explain what you want :)…