ells and offset it and then split it.
1) extrude the origional surface
2)make a 3D voronoi around it
3) find the intersecting surfaces of the two geometries
4)hide the rest
5) offset the surfaces to give some thickness to the material
6)split the polysurface with the origional voronoi
Or
4) use weaverbird window (I think it's called, the green square with a hole in it)
5)split the polysurface with the origional voronoi…
Added by Jack Young at 1:00am on November 29, 2016
)
3. KeyError(1417,)
4. KeyError(1417,)
5. KeyError(1417,)
6. KeyError(1417,)
7. KeyError(1417,)
8. KeyError(1417,)
9. KeyError(1417,)
10. KeyError(1417,)
11.......
i tried different weather file but also same result. it seems i have same problem. the file am working on is the radiation file i took from the examples . whats seems to be the problem?
thank you for your time…
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!…
Integer = 0 To 9
val *= 2
lst.Add(val)
Next
Since val is a ValueType, when we assign it to the list we actually put a copy of val into the list. Thus, the list contains the following memory layout:
[0] = 2
[1] = 4
[2] = 8
[3] = 16
[4] = 32
[5] = 64
[6] = 128
[7] = 256
[8] = 512
[9] = 1024
Now let's assume we do the same, but with OnLines:
Dim ln As New OnLine(A, B)
Dim lst As New List(Of OnLine)
For i As Integer = 0 To 9
ln.Transform(xform)
lst.Add(ln)
Next
When we declare ln on line 1, it is assigned an address in memory, say "24 Bell Ave." Then we modify that one line over and over, and keep on adding the same address to lst. Thus, the memory layout of lst is now:
[0] = "24 Bell Ave."
[1] = "24 Bell Ave."
[2] = "24 Bell Ave."
[3] = "24 Bell Ave."
[4] = "24 Bell Ave."
[5] = "24 Bell Ave."
[6] = "24 Bell Ave."
[7] = "24 Bell Ave."
[8] = "24 Bell Ave."
[9] = "24 Bell Ave."
To do this properly, we need to create a unique line for every element in lst:
Dim lst As New List(Of OnLine)
For i As Integer = 0 To 9
Dim ln As New OnLine(A, B)
ln.Transform(xform)
lst.Add(ln)
Next
Now, ln is constructed not just once, but whenever the loop runs. And every time it is constructed, a new piece of memory is reserved for it and a new address is created. So now the list memory layout is:
[0] = "24 Bell Ave."
[1] = "12 Pike St."
[2] = "377 The Pines"
[3] = "3670 Woodland Park Ave."
[4] = "99 Zoo Ln."
[5] = "13a District Rd."
[6] = "2 Penny Lane"
[7] = "10 Broadway"
[8] = "225 Franklin Ave."
[9] = "420 Paper St."
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 6:26am on September 9, 2010
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
simplified in the bake name attribute and on the bake object component. I was counting on maintaining that structure.
{0;4}
{0;4}
{1;2}
{1;2}
Easily fixed with an additional attribute. Just curious on the behavior. Thanks.
…
Added by japhy to EleFront at 3:18pm on October 9, 2017
13 5 15 6 17 7 ... …
But it seems I have not been clear:
the input values (3,5,7,9,11,13) should be presented in the way of "number slider" parameter. So by increasing the value of the slider from minimum 3, to 5, 7, 9, 13, 15, 17... I should get an output numbers of 0,1,3,4,5,6,7...
So I if choose value 3 on the input "number slider", on the other end, I want 0 as an output.
Or if I choose value 5 on the input "number slider", I want 1 as an output, and so on.
Is this possible?…