} (N=11) {0;1} (N=11) {0;2}(N = 11) {0;3}(N = 11) {0;4}(N = 11)
2. I run the Points that are coming out from the Divide Curve Components through the Path Mapper components with this definition:
{A;B} (i) > {A} (i)
3. I run data coming out from Path Mapper component through:
a) Parameter Viewer component and the result is:
{0} N=11 (data with 1 branches)
b) Point > Panel and the result is:
collection of 11 point (N=11) which is the exactly the same as the collection of point belonging to {0;4} (N = 11).
So, here is the question:
why the collection of points coming out from the Path Mapper {A;B} (i) > {A} (i) component is the same as the collection of points belonging to the curve {0;4}(N = 11) ?
Anyway ... It 's the first time I ask a question here... so I would like to thank you for what you do with your work! Thank you! You are really great!…
ve a Vertex [V] connected to four other Vertexs [N1-N4].
Each of the has a Value:
V ... 1
N1 ... 5
N2 ... 3
N3 ... 8
N4 ... 11
The Average Filter would set the Value of [V] to
(1+5+3+8+11)/5 = 5,6
The Median Filter would Sort Values and pick the middle one
1,3, [5], 8, 11
Hope that helped...…
This must be a bug because its true for dividing by all odd numbers:
(i-1)/3
(i-2)/5
(i-3)/7
(i-4)/9
(i-5)/11
....
(i-n)/2n+1
And you can't make it work for even numbers
Added by Danny Boyes at 5:06pm on January 13, 2010
where each branch contains all the points generated by dividing each curve, so if you divide into 10 segments, you'll get:
{0;0}(N = 11)
{0;1}(N = 11)
{0;2}(N = 11)
{0;3}(N = 11)
{0;4}(N = 11)
Where the second integer in the curly brackets refers back to the index of the curve in the original list.
Another way to look at this data is to see it as a table. It's got 5 rows (one for each original curve) and 11 columns, where every column contains a specific division point.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
ee 3)
{5}
0 15
{6}
0 16
And I want to place points at every possible combination of these coordinates, treating Tree 1 as X coordinates, Tree 2 as Y coordinates, and Tree 3 as Z coordinates. Also, I would like the list of points to be a tree with paths corresponding to the coordinates. Wouldn't it be nice if I could plug these trees into a Point XYZ, with a new "branch cross reference" method, and get the following result?
{0:3:5}
0 {10.0, 13.0, 15.0}
{0:3:6}
0 {10.0, 13.0, 16.0}
{0:4:5}
0 {10.0, 14.0, 15.0}
{0:4:6}
0 {10.0, 14.0, 16.0}
{1:3:5}
0 {11.0, 13.0, 15.0}
{1:3:6}
0 {11.0, 13.0, 16.0}
{1:4:5}
0 {11.0, 14.0, 15.0}
{1:4:6}
0 {11.0, 14.0, 16.0}
{2:3:5}
0 {12.0, 13.0, 15.0}
{2:3:6}
0 {12.0, 13.0, 16.0}
{2:4:5}
0 {12.0, 14.0, 15.0}
{2:4:6}
0 {12.0, 14.0, 16.0}
In this form of cross referencing, every combination of individual branches from the different lists is used as separate input, and the output for each combination is put onto a branch in the result whose path is the concatenation of the input branch paths used.…
Added by Andy Edwards at 7:03pm on November 3, 2009