e! I do not have good ideas today!
The end result of the list would be:
5, 10, 15, 20, 21, (21 + 5), (21 + 10), (21 + 15), (21 + 20), (21 + 21), (42 + 5), (42 + 10), (42 + 15), (42 + 20), (42 + 21), etc …
cture, Rhino treats them as a single flat list. For example a surface can have 10 rows and 6 columns of control-points, resulting in a list of 60 points.
But 10 times 6 isn't the only way to get to 60. If you want to make a surface out of a list of 60 points, you'll also have to tell Rhino how those 60 points should be interpreted in terms of a grid. It could be 2*30, 3*20, 4*15, 5*12, 6*10, and all of the aforementioned products the other way around.
Sometimes there's only one way for a number of points to fit into a rectangular grid. For example if you provide 49 points, then 7*7 is the only way to make it work, but these cases are rare so we always demand you give us all the information required to actually make a rectangular grid of control-points from a linear collection.
As for "Why is it, sometimes we need to attach additional value into it?", this is usually because when you divide a domain or a curve into N segments, you end up with N+1 points. For example take the domain {0 to 5}, and divide it into 5 equal subdomains. You end up with {0 to 1}, {1 to 2}, {2 to 3}, {3 to 4} and {4 to 5}. However there are six numbers that mark the transitions between these domains 0, 1, 2, 3, 4 and 5. This is why you often have to add 1 to the UCount, because the number that controls the UCount often results in N+1 actual points.…
Added by David Rutten at 8:30am on December 25, 2014
cannot install gh ver 51 for rhinọ 5 ( i'm using the last rhino 5 trial 90 days). in my PC have both Rhino 4 & 5 .when i install GH it alway defaut install for rhino 4. plz help me !
, branches, and trees.
This is currently how I think of it:
A 'point' component with 5 points will generally be compared to a 1-dimensional array with 5 indices.
If we flip this "path" then it becomes a 2-dimensional array looking like this [5][1].
Although it seems like Grasshopper does not iterate through these 'arrays' as one would assume.
Also, the question arises when we have a "tree" whose "paths" looks like:
{0;0;0} (5)
{0;0;1} (5)
{0;1;0} (5)
{0;1;1} (5)
{1;0;0} (5)
{1;0;1} (5)
{1;1;0} (5)
{1;1;1} (5)
For example.
Anyone have any insight here? Or where insight may be found.
Thanks!…
ok thanks, i solved the problem on 4, but not on 5. i guess i'll have to update 5. 4 needed the latest vcredist_x86 from microsoft. hope that helps others
What is weird is that i tried this in both 4 and 5 with different results. I created a rectangle and did a planar srf command. In 4 control pts were at the edges but in 5 they were offset.