Path Mysteriously Disappearing from Surface Closest Point to Evaluate Surface

Replies to This Discussion

Permalink Reply by johnnyUtah05 on July 16, 2015 at 9:05pm

Any takers? Good times here :)

Permalink Reply by peter fotiadis on July 17, 2015 at 12:56am

My dear Watson

See the Dark Side first > since each closest pt gives us 2 values (u,v) we ... need some "further" classification or not?

Attachments:

• apples_to_sardines_V1.gh, 53 KB

Permalink Reply by peter fotiadis on July 17, 2015 at 1:26am

forgot to add vectors and planes in that C#

Attachments:

• apples_to_sardines_V2.gh, 59 KB

Permalink Reply by johnnyUtah05 on July 17, 2015 at 9:57pm

Thank you for the C# Mr. Bell. Good point you make about the boolean being false... Seems logical that that is where I was mistaken. I gotta learn to write script like you. I've learned some python but GH is written in C# so hmmm....

Permalink Reply by peter fotiadis on July 18, 2015 at 1:12am

Get rid of the Elise, buy a M3 (even secondhand).

Permalink Reply by FRiou on July 17, 2015 at 1:06am

Hello Erik,

I think your problem comes from your data structure in the surfaces tree you're using as input.

If you visualise the output from your Surface Closest Point component, this is what you get :

I think you're looking for something more like :

In this situation, your output tree structure is OK.

Permalink Reply by FRiou on July 17, 2015 at 1:22am

Oh, and here is the definition of course...

Attachments:

• Path Disappearance FRiou.gh, 30 KB

Permalink Reply by johnnyUtah05 on July 17, 2015 at 10:08pm

Thank you for your reply FRIou. 

@FRiou I agree it must have been a problem with the surfaces, but what got me confused was the data structure of the curves in relation to the surfaces. Usually the surfaces and the division points sync up. It seems you duplicated the values of the surfaces to the same value as the points. Is this where I ran into problems? Normally I don't need to do this I don't believe; however, in this case it makes sense. 

Thank you again. 

Erik

Permalink Reply by FRiou on July 20, 2015 at 12:46am

Hello Erik,

Your problem was that there was no coherence between your points tree structure and your surfaces tree structure.

Your points tree was like {# of surface;# of curve}(list of points on curve) i.e. the points on the 5th curve of the 3rd surface where in branch {3;5}.

Your surfaces tree was like {0;# of surface} i.e. your 3rd surface was in branch {0;3}.

So you asked your Closest Point on Surface component to match your {3;5} points tree branch to your {0;3} surfaces tree branch... components are smart but not that smart.

So you need to have a surfaces tree structure corresponding to your points tree structure, i.e. for each {3;x} branch of your points tree, you need a {3;x} branch in your surfaces tree with your 3rd surface in it. Hence the duplicate.

I hope this clears it up a bit.