Branch training, right path?

I try to write “cleaner definitons” with less commands and try to understand the branches better.
Normally i would have had 2 move commands and 3 extrusion commands. One for each row.
I finally figured out a smoother way for my example.


Its just a simple start of an irregular aluminium shelf:

  • Is there a better way to merge the 3 main branches other than explode and Entwine. What if i have 200 branches and i need to add 1?
  • I got to that beatifull tree that just looks as i want it to be, but in order to extrude it i have to trim it. Is there an other way to extrude & keep the Tree shape?

I just noticed that i could have made a surface from the curves in order to jump that group ungroup command.

I will be happy about criticism!


Old file without internalized data:

2024-11-27_Test.gh (10.1 KB)

Internalise your curves.

1 Like

Thanks! I really didn’t know about this, it makes my life so much easier! :face_with_peeking_eye:

Here the new File to look at it:

Even if the script changed there are still my 2 questions, someone might have the power to enlighten me :slight_smile:
2024-11-27_Test_2.gh (18.7 KB)

the only thing I would say, because you are not moving your original Surfaces, it’s easier if you add a zero vector in the Move list and avoid the entwine:

2024-11-27_Test_2_Re.gh (20.1 KB)

everything else looks fine to me, deciding to move first and array then or the opposite is just a matter of personal preference :+1:

1 Like

Thank you for your time!

I continued a bit but it got a bit messy, it works so far a bit slow because of the many edges.
Only the Block inside the gh-Script is not working yet perfectly.

2024-11-27_Test_3.gh (209.1 KB)