Bug? GH v0.8.0001 IntCrv 'Kinky'

Hi David,

GH seems to create an interpolated curve unlike that of Rhino's. Is this a Bug? See Image below and attached file for points.

Attachments:

IntCrvKinks.ghx, 126 KB

Replies to This Discussion

Permalink Reply by David Rutten on November 10, 2010 at 11:08am

Hi Danny,

there were four duplicate points in that list (indices 39, 45, 51 & 57). If you remove those (Cull Index) then the curves in Rhino and Grasshopper seem to be identical. Am I confused?

--
David Rutten
david@mcneel.com
Seattle, WA

Permalink Reply by Danny Boyes on November 10, 2010 at 12:23pm

That might explain it. I don't get why when I baked the points from these list and made the curve why rhino in should it be different.

Permalink Reply by David Rutten on November 11, 2010 at 1:12pm

I think Rhino might be smart about it. There's usually quite a lot of 'smarts' in commands that are not ported to SDK functions as we expect programmers to be smart on their own behalf :)

--
David Rutten
david@mcneel.com
Seattle, WA

Permalink Reply by Shawn Fernandez on November 11, 2010 at 8:50am

I have also been getting occasional odd results from Interpolate Curve where the curve extends past the end point and loops back towards it. Usually the loop is so tight that you can't see the difference. It just looks like the line extends past its end point. Since I'm using the endpoint to generate a tangent, it really messes up the definition. I have found that changing the number of input points typically removes the issue, but it brings an uncomfortable level of uncertainty into the solution.

RSS