Network Surf component bug

Replies to This Discussion

Permalink Reply by Hyungsoo Kim on March 19, 2016 at 9:52pm

It's crucial that you follow the sequential order when you inputting the curves into the network curve component.

Attachments:

• NetworkSurfBUG_re.gh, 42 KB

Permalink Reply by Olivier Suire on March 19, 2016 at 11:10pm

Hi Hyungsoo,

Thanks for your help.

I do know that curves need to be sorted for NetworkSrf to work.

That is why I used a "Merge" component, thinking that the input order was actually maintained, but I realize with great disappointment that it isn't.

I'm really perplexed by this, having used it so many times.

What is the point in having multiple distinct inputs, if the stuff is jumbled afterwards ?

This has to ba a bad dream...

Attachments:

• Merge messes stuff up.jpg, 71 KB

Permalink Reply by Hyungsoo Kim on March 19, 2016 at 11:51pm

Hi.

Now it's likely to find the cause. You'd be better off collapsing data tree structure of curves before inputting into "merge".

Attachments:

• NetworkSurfBUG_rev2.gh, 43 KB

Permalink Reply by Olivier Suire on March 20, 2016 at 12:00am

Phewww ! OK, that makes sense (kind of)

Not sure why the tree structure interferes with the order, but indeed, that was the issue.

The "automatic grafting" paradigm set me a trap here...

Yet another example how data trees can be evil :)

Thanks a lot Hyungsoo.