Hello guys,
I am trying to recreate a definition that is here in the forum, but the part highlighted in blue cannot decipher it, I want to use nodes to have a clear idea of the definition. Any suggestions?
Trying to be as complete as I can here, as there are a LOT of concepts at play with lists, nested lists, variables in lists, and lacing calls… Hopefully this will be enough to help you out.
Everything inside the carrots < >relates to lacing. Ignore those for now and we’ll discuss them later.
p2 is a new variable, defined as everything after the equals sign. List.Flatten means the list is having a level (or more) discarded.
The p1 is the point list which was defined as a variable above. Hopefully you get that as I am only describing this one line.
The .Translate bit means you’re calling on the Geometry.Translate function, in this case using the X,Y,Z method so inside the brackets we’ll be expecting 3 doubles for the X value, Y value and Z value representing the distances to move each point along the respective axis. These are separated by commas and are given in order.
The [0, S*1.5], is your X value. The brackets define a list so we have more than one distance on the X axis. The first distance is 0, and the second is the variable S multiplied by 10.
The Y value is [0, A], so we again have a list indicates by the brackets. The first item is 0 and the second item is A, another variable defined above.
The Z value is given as a single 0, and then the translate function is finished off with the close parenthesis. The List.Flatten function receives its last variable, hard coded as 1, and then that function is also completed with the close parenthesis before ending the P2 variable line with a semicolon.
Now to review the lacing we can go back and decipher the carrots. A complete lack of carrots to indicate lacing means Dynamo will utilize auto lacing - the equivalent of placing a node and not adjusting your lacing. The presence of < X > after a single variable will trigger your lacing options. X can be any positive integer less than 999999999, and the value, or more specifically the relationship of this value to other lacing triggers will alter what is performed. The low value at the first level, followed by the matching high value at the subsequent levels means you’ll get longest lacing applied to the first input.
3 Likes
Jacob thank you for your answer and for sharing your knowledge. Excellent.
But I still have a little confusion and, it is the meaning <2> <2> after the variables and not <1> <2> to get the cross product (which is what I deduce) why?
Can you share that .dyn so I can work with that instead of having to reproduce? Will save me some time. Thanks.
@davidaweil79 You’ll need to alter Levels, not Lacing to get the same result with nodes
hex.dyn (37.4 KB)
Providing the link usually helps
1 Like
Thank you Vikram, thank you Jacob, a hurray for you. Now I have it more clear.
1 Like