Contour component - branching bug?

[DanielK1 (Daniel Krejci)]

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

Input surfaces with branches:
{0;0}
{0;1}
{1;0}
{1;1}
{1;2}

Expected contoured data structure suppose to be:

{0;0;?}
{0;1;?}
{1;0;?}
{1;1;?}
{1;2;?}

But it is something:

{0;0;?}
{0;2;?}
{1;1;?}
{1;3;?}
{2;4;?}

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

Or did I miss something?

Files:
Contour-bug.gh (18.5 KB)

[magicteddy]

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