I am trying to compare different Visual Dataflow Modelling tools and for that purpose I am building a Kilian roof in each of these tools. In Dynamo, I would like to subdivide the surface into a list of polysurfaces over which I would perform other functions like create diagonal cross lines etc. Im stuck at subdividing the surface and cant find an effective node to do the same. Am I missing something? Can anyone help me with it? File is attached. Thanks!!
I understand that you are trying to follow this workflow from Axel Kilian
After generating the surface you can directly make the networks of points with just PointAtParameter
You will find different custom nodes for takings group of 4 points, the quads (some of them will make it directly in the surface without having to use PointAtParameter before)
With the quads is up to you to make the diagonals with revit adaptive components or with the solid tools of 0.7 (a DS function will be quite handy in this last case)
Side note to the last post:
I have taken a look to the existing custom nodes for quads (how they work internally). They were done in the previous versions. They are quite smart, but maybe a little bit too complicated compared with the way you will do it today using the new engine.
Getting the quads with designscript is very easy and straightforward.
Having the net of points (list of points with dimension 2), you can get the quad of a point with its indices
def QuadAtPointIndices(NetPts: var,N1,N2)
Now you can nest it in other function for getting all the quads from a net of points
Or even more simple if you are making the net of points only for obtaining the quads
def QuadsAtSurface(Surf, U1,U2)
Thank you so much, Eduardo. I have actually been trying to script as less as possible and use as many built in nodes. Nevertheless I have tried out the method outlined above and it works well. However, I am stuck at the next point. I have created a custom recursive node that would add diagonal lines for each quad of points. But the node doesnt seem finish execution at all. I have kinda made sure it doesnt get into infinite looping, but still no luck. Even the downloaded recursive nodes do not seem to work in 0.7.0. Is it a version issue? Any idea? I have attached the files for reference. kilian_coding2 quads_diagonal
Vignesh, Recursion currently doesn’t work in 0.7.0, but I hear it will be back eventually.
You are welcome.
First, nothing stops you to put the DS functions inside of a custom node
(By the way, this custom node is already uploaded in the package manager)
About the recursive node, I am sorry but I haven’t used them so I can not help you on that. But maybe someone else here can.
In any case, you have done pretty much what is needed, because you have defined how to get the diagonals with a list of four points.
The only problem now is how to evaluate one by one the sublist of 4 points. But you don’t need any special list management workflow for that. In fact, you are almost there…
If this is working for a list of four points …
…this will work for any list of four point and Dynamo will take care of any needed list management.
When you define the argument Points as “Points:var”, instead of only “Points”, you are telling that the function expect a list of dimension 1. Points:var mean that the function expect a list of dimension 2 and so on.
The DS function can take directly the global lists of quads. You don’t need even to flatten it one level before.
And as I said, you can put the function in a custom node. Even integrate it with the one that make the quads for having an “all in one” node that makes all the step of your workflow
I didnt know Dynamo could manage lists this way. That was very useful. Thanks a lot, Eduardo.
But, I am trying to create a model with as little multi-line scripting as possible since I am comparing dynamo with other VDM systems like Grasshopper, GC etc. I would like to know if the recursive function I created would be the best bet to achieve the diagonals from the list of quads using nodes (if at all it works in 0.7.0). Any chance I can reduce the overall number of nodes?
The DS Function is the more robust, efficient and concise way. But If you prefer not to use it, you can manage this via transposing the list of quads
As always, you can integrate this very easily in a custom node.