Onion nodes – AutoJoin workflows

We have recently released an update to our Dynamo node package – Onion. It can be found in the standard package manager.

Now, we want to show some possible workflows with the package – starting with AutoJoin nodes.

Join intersecting elements automatically

So, let’s say you have a large architectural model and want to generate a few sections. One of the things you have to do in order to make it look nice is to join all the walls and floors visible. Quite a lot of work. See how it can be automated with our nodes :

It is very simple indeed. You just have to input two element lists and voila! After you run the script intersecting elements will be joined.

In the example above we take all the elements of the Wall and Floor categories. The node is a compiled C# code – so it is much faster than standard Dynamo workflows.

Unjoin not intersecting elements

Revit can give you warnings, loads of warnings. Often they involve elements that have been joined but now, for some reason, their geometries are not connecting.

With our Unjoin node you can automatically go through all such warnings and disconnect the elements:

The node requires no setup actually – you just run it. If you want you can see what elements have been processed.

That is all for today. Soon we will publish some more Onion nodes workflows.

Posts created 45

2 thoughts on “Onion nodes – AutoJoin workflows

  1. Hi. So I tried this node written in C# you recommended (here http://lubim.co/2019/07/01/efficient-auto-join-using-dynamo/#comment-2520) and it is probably the most useful tool for joining elements I have worked with. I would even say that even better than those you have to pay for.

    I started with simple operations (few elements) and at the end It analyzed around 3000 elements and made a bit more than 1000 joins. I decied to give it the full load of the project but it came out with an error. Never mind. There are around 20 types which needed to be joined in various combinations so I always filtered out only two and run the graph. At the end I was able to reduce the intersections from 3000 to 75 in 2 hours. Great work!

    I only experienced one anomaly. I was able to join most of the touching elements too. However there were one or two types which were not able to join when touching. I do not know why. It always was a wall with height less then 300mm. Idk if it means something or not. Other than that it works perfect for me.

    1. Hi! Once again thanks for the feedback, I am really really glad it works and you find it useful. Thennodes basically share the same algorithm/code therefore there might be same issues, like the one with touching elements. I plan to look into that and hopefully fix it soon (if the problem is what I think it is). Should be within two weeks with the next package update.
      As for the other errors I can also look into them, always happy to try to make things better. Although if they are Revit model specific (like “can’t cut joined element”) then it might not be possible, because it would be a Revit internal issue…
      You can always drop me a line at lu@lubim.co.

Leave a Reply

Your email address will not be published.

Related Posts

Begin typing your search term above and press enter to search. Press ESC to cancel.

Back To Top