and says "repeat every Nth element", meaning say if N was 3, I would get A B C C D E F F G H. I would also like to be able to then insert a list of 3 elements in between each of the repeats. For example, I wanted to insert: 1. 1
2. 2
3. 3 into the list, I would get A B C 1 2 3 C D E F 1 2 3 F G H. It seems like an easy task, but I cannot for the life of me figure out how to do it, I must be making a very basic mistake. I am new to grasshopper, so any and all help I could get would be GREATLY appreciated!…
ace. What I am trying to do is then take these indexes and arrange them to fit a grid - so that all shared edges meet up. e.g. Surface 0 shares edges with surfaces 7 and 8, surface 7 shares edges with 19,4, 3, surface 3 shares and edge with 8 etc. What I need to do is graphically represent this in a grid, so that I can map out the uvs and effectively solve the problem of surface seams. Does anyone have a clue how to do this kind of 2d shuffling?…
a follow up question... how do I wrap a list onto itself at a certain frequency?
i.e. I want the list {1;2;3;4;5;6;7;8;9}
to become {1,4,7; 2,6,8; 3,6,9} wrapped every 3rd item
Added by Joshua Jordan at 5:30pm on November 17, 2012
Hi,
I want to divide curve with distance between points so it will be like this:
1--2---3----4-----5------6-------7-----, ...
with values in range 1 to 50, must be simple but im stuck..
tnx
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.
…
en 3 of them, and one poolyline between two of them.
It would also be very nice if i could control it so that only the successive ones can be connected
so if {0:0:0} has 8 points and {0:0:1} has 8, as do {0:0:5} and {0:0:6} i would like to have this as two polylines, not one continoous that would in this case jump three branches (or curves that are shorter).
Does this make any sense?…
Added by Dusan Bosnjak at 2:08pm on September 28, 2009
.#...
In parameter viewers, we see the number inside the branches remains while going through components (a list of 4 branches of points like {1},{3},{4},{7) put into a polyline component returns an output of polylines with branches {1},{3},{4},{7}).
This was easy to handle, straightforward.
pic2. Grasshopper 0.9.#...
passing through certain components the input branches {1},{3},{4},{7} get "reset" as follow:
{1} becomes {0}, {3} becomes {1}, {4} becomes {2}, {7} becomes {3} etc...
So far the way around this that I know is to replace branches afterwards, but in a real-life GH definition it soon gets extremely fastidious. Not talking about fixing older GH files that get messed up when opened with GH 0.9.#...
Must be a smarter way I'm missing on.
Is there somewhere a setting to get back to the more user friendly GH0.8 way. And some solid reason behind this change?
Thanks.…
rray of cables, fasteners and other useless stuff.
PS: one issue brings the other :
There's some components that respect the tree and others that do whatever they want.
For instance imagine 23 line sets that belong to 3 branches (the facade profiles). If you apply Divide curv (say with 7 divisions) you expect to get back 23*7 points in 3 branches....not the case I'm afraid.
However if you apply Eval Curv with just one value for t > you get 23 points in 3 branches.
Moral: more red Russian vodka required (+ a decent cigar)
…