Data structure on tree level

Hello!

I have some problems with data managements in grasshopper. I am trying to subdivide multiple surfaces with different U and V values, which means I want to get different the surfaces with different UV division based on my previous variables.

The problem is I can manage to create some patterns on a surface level, but could iterate the process in tree level.

post your GH file with internalized geometries

posted.gh (12.5 KB)
Here is the file!

I included two surfaces, but want to iterate this pattern generation process in all the input surfaces with different UV values.

I’m just wondering why you don’t use Isotrim?

See attached
posted_Isotrim.gh (13.6 KB)

I think both are almost identical in terms of the thing what I want to do.


The problem is to iterate zigzag pattern process in all the surface inputs… but I could manage it in only one surface level, not in surfaces level (tree level)…


posted_Solved.gh (8.8 KB)

Totally Missed the Zigzag, Thank you for pointing it out , here are the issues I found with your definition.

1- Simplify is a destructive tool, It removes some branches that are sometimes needed downstream, so try to avoid it if necessary.
2- since your tree gets more complex. flipmatrix doesn’t work either, so use Path mapper.
3- Match tree is your friend, so use it more.

You can have as many surfaces as you can, I just forgot to cull the last polyline since it doesn’t have a zigzag pattern

1 Like

Awesome! It is a good example to learn tree structure. :slight_smile: Thank you for your clear explanation as well!

1 Like

You’re welcome