onsecutive points at the same height then your 'Break at discontinuities' component eliminates the middle point completely and then the 'Interpolate Curve' component gives a much bigger bump in the wrong direction. This was enough to get curves to meet from opposite sides.
I fixed this by changing the heights to 1.1 or 2.9, rather than 1.0 and 3.0, but it took a little while to work it out! Sigh.
I attach a new version. But I actually preferred it as it was before. See what you think!
Bob
p.s. in the first list, elements 11, 12, 23 and 24 go from 1 to 3; elements 17 and 18 go from 3 to 1. In the second list, elements 6, 17, 18 and 29 go from 1 to 3; elements 12 and 23 go from 3 to 1. Given the above fix, these can be easily seen.…
Added by Bob Mackay at 10:40pm on November 24, 2015
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.
…
o now is select and group together list items by their index. {0:0} and {2:0} also {1:0} and {3:0}. They way I'm doing this at the moment is quite complicated and I'm sure there's an easier way to achieve the same result.
maybe someone in here knows a solution?
thanks a lot…
;1},{0;2},{0;3}, (note that the first item is NOT {0,0})
{1;1}{1;2},{1;3},
{2;1},{2;2},{2;3},
{3;1}{3;2},{3;3}...
Well I'll just upload an extract of the definition. The data path should be the same, but with the items in the last path shifted to the first path, and the items in the first path shifted to the second path and so on.
I'll keep trying. …
o Grasshopper and Rhino.Schedule: Rhinoceros1. NURBS and Mesh geometries.2. Complex geometries.3. GH to Rhinoceros workflow.Grasshopper1. Introduction to parametric design2. Parameters and components.3. Math and logics.4. 2D and 3D modeling.5. Simple definition6. Application to typical deisgn problems.SoftwareRhino + GrasshopperVenueParametric Support, Hardenbergstrasse 38, BerlinFee[Early Bird] 400 eur + VAT (until 11/11)[Regular] 420 eur + VAT[Student] 300 eurMore:hello@parametric.support…
Is it like this:
If a beam is connected from nod 0 to 1 and from 1 to 4. Another from 2 to 3 and from 3 to 5.
Node 1 and 3 have the same coordinates, but are they rigidly connected or not?
ea being the further up the column, the more dramatic the effect. For example:at 1", the effect is at 1at 3", the effect is at 3at 7", the affect is at 7, ect.I figure it must be some form of formula, but I am uncertain how to call upon other number sliders, or how to set it up.Thanks!…