wunderbar ^^* !
maybe you would be interested in Jun Mitani's work ?
www.flickr.com/photos/jun_mitani/mitani.cs.tsukuba.ac.jhe published two books (keyword : 三谷 純)立体ふしぎ折り紙
ふしぎな 球体・立体折り紙
uplicatePoints i find 21 different points.
how i can find the duplicated ones and put them in a list in python?
i've also tried the set method but it seems not working with points.
thanks in advance!
best
…
ult, my 3dm is very large.
Another problem, when the fonction is ok, the draw in grasshopper is ok, when i bake i have only a litte part of the opération.....
If you could help me, thank you
[Edit] Here the description in the null item :
{0;0}0. Brep: brep.m_T[43047] trim is not valid. trim.m_type = seam, the edge is manifold, but brep.m_L[trim.m_li=1114].m_type is not outer.brep.m_L[1114] loop is not valid. brep.m_T[loop.m_ti[21]=43047] is not valid.brep.m_F[0] face is not valid. brep.m_L[face.m_li[1114]=1114] is not valid.ON_Brep.m_F[0] is invalid.1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. …
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
Tree:
{0;0;0} N = 2
{0;0;1} N = 1
{0;0;2} N = 3
{0;1;0} N = 5
{0;1;1} N = 8
{0;1;2} N = 10
If we apply the aforementioned mapping to this tree, we'll end up with the following result:
{0;0} N = 6
{0;1} N = 23
Basically {0;0;0}, {0;0;1} and {0;0;2} are combined into a single path {0;0} as we disregard the third index because "C" is no longer present in the target mapping.
Because we only use the Mapper to modify paths, we do not lose any data items, though we might lose some of the paths.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 1:03pm on August 25, 2010