Contour component - branching bug?

Hi, I find out strange behavior of “Contour” component.

Input surfaces with branches:

Expected contoured data structure suppose to be:


But it is something:


Not sure if I explain well, I am attaching file which showing expected result vs bad one.

Or did I miss something?

Files: (18.5 KB)

1 Like

Same thing here and even worse, the order of the output branches is incorrect !
It seems the component takes {x;y} and transforms it into {y;i;*} with i =0,1,2…

Only workaround I can think of right now if to Match Tree with a simple 1-level tree structure before and match again after.

Or use Entwine to avoid dropping that first number :man_facepalming:

1 Like