Show messages:
1-17
18-22
From: bemfarmer
Hi Karsten,
Thank you very much for all of the information and examples.
- Brian
From: bemfarmer
PointArray Documentation and Parsing to Clusters
This post is a request for clarification, and a preliminary attempt to document the PointArray, and a request for clarification of the length parameters, etc..
It is also a suggestion for a new “Parsing” node.
So far, for myself, the (inner organization) data structure of the PointArray, and the separation of a pointarray into clusters, and superclusters of points is not clear, nor intuitive as to how to do it. Karsten has described the SplitPts node and the PointsExt node which are helpful. The last 3 entries of the ArrayLogger node are the xlength, ylength and zlength.
The points in a pointarray are more than just raw points coordinates of (x, y, z).
Seven of the 10 properties of the pointarray are pt.x, pt.y, pt.z, Rx, Ry, Rz, and Scale.
Somehow Frame fits in here?
And what is the purpose of Scale. How, where, and when does it cause Scaling?
The other 3 properties are:
The xlength is ? The number of points in a cluster? Starts at 100, and divided down to 20 in Karsten’s example.
xlength is rounded in some way to an integer.
The ylength is ? The number of clusters? (5 in Karsten’s example.)
Tells Ucurve to start or stop?
If the number of points does not divide evenly, some points are used twice?
The zlength is ? Some other index???
The “Parsing” node would have:
Input for a PointArray. (100 elements)
Input for the number of points in a cluster. (xlength?)
Input for the number of clusters. (supercluster?)
Input for grouping several clusters. (supersupercluster?)
Output a pointarray which the convertpts node, or the curve node will create separate curves for.
Another node which will group separate curves together according to the supercluster number…?
The points in an objectarray are MoI3D geometric, displayable entities. They are much more than a raw point,
and are different than a pointarray.
- Brian
I tried using some hex polygons as input, with strange results. I want to map the sides to curves...and recombine...
From: Karsten (KMRQUS)
Hello Brian,
at first - yes it's a frame description:
x,y,z, Euler-angles (x,y,z by using rotation order x,y,z), scale mostly 1 (useful for some programming - can be used as scale factor or for transformation proposes (homogenous coordinates).
The x-length, y- length, z-length is an organizations structure. For most of the things one value would be enough, but if you have a look to the points node it organizes the output in rows, columns and levels. Depending on the node that gets the info the processing can be differ. Please have a look to the points node with the unum, vnum and wnum values that set exactly the values in the pointarray at the output. The convertPts in U-Mode uses xlength as the number of points for a curve and ylength*zlength=number of curves. In W-Mode it uses the y length for the number of points and xlength*zlength = number of curves. The curve node takes x-length as the number of points for a curve and zlength for the number of curves. Typically these details should be hidden for the user, but sometimes you need them for special things. Please play with this node and look to the results and the array logger.
I hope that brings a little bit light to the tunnel.
Have a nice weekend
Karsten
From: bemfarmer
Thank you Karsten. Your explanations should help a lot. (So I should have studied the .js code...:-)
- Brian
W=V
From: bemfarmer
Nodeeditor node graphics PDF.
- Brian
Deleted to make space.
This was just a picture of most of the nodes.
Show messages:
1-17
18-22
