Moving Crv Start Pts to Acute Angle

Replies to This Discussion

Permalink Reply by Danny Boyes on May 26, 2011 at 7:51am

Updated

Try this:

If you saw the previous one. I connected the wrong wire to the synchronous sort.

Attachments:

• sortStartPoints.ghx, 114 KB

Permalink Reply by Yoann Mescam (Systemiq) on May 26, 2011 at 7:53am

If you really want to use Galapagos, you should do something like that:

(set the number of digits to 6 in the slider)

The trick is just to test the angle between the point on curve, and the 2 points just before and after it.

It will probably faster to use Discontinuity if you only have sharp angles though.

(Just saw Danny's solution, even better).

Permalink Reply by kleerkoat on May 26, 2011 at 9:18am

thank you for the replies, I'm going to go over them and see what's going on with them.

 

I'll probably be back with some more questions. ;-)

 

thanks again!

Permalink Reply by kleerkoat on June 26, 2011 at 4:37pm

ok, so I've got it worked out thanks to you guys and it's working wonderfully.

 

But now there is the question of how do I change those curve's start points to the point that it's found?

Attachments:

• moveCrvStartPoints.ghx, 125 KB
• moveCrvStartPoints.3dm, 996 KB

Permalink Reply by Danny Boyes on June 27, 2011 at 2:13am

Hi Ryan,

 

with my method you would just need to set the C input to True on the Polyline Component to close it and thus make a new version of the triangle.

 

Permalink Reply by kleerkoat on June 27, 2011 at 6:39am

Hey Danny,

 

The curves that I am running this on are curves that are created elsewhere in my definition, or will be curves that are already created in Rhino.  So I can't really redraw/recreate the curves like your definition.

 

I did end up going with yours as you can tell by the latest uploads, I had to tweak it a little to just pick the most acute point on a bunch of curves. 

 

I'm just stuck now at the part of saying, take these curves and move their start point to this point.

 

Thanks again,

ryan

Permalink Reply by Danny Boyes on June 27, 2011 at 7:20am

Because you have sorted all of the points from your referenced curves you can then recreate the new polyline. Unless your curves are not closed polylines

 

Permalink Reply by kleerkoat on June 27, 2011 at 8:06am

hmm, I don't think that will work because I'm dealing with polycurves, they are all closed though.  i don't think recreating the curves from the sorted points is going to work right.

 

thanks again for helping me out with this,

ryan

Permalink Reply by Danny Boyes on June 27, 2011 at 8:48am

What about this?

EDIT: w should be set to true on the Shift Component for the curves

Attachments:

• moveCrvs.ghx, 135 KB

Permalink Reply by kleerkoat on June 27, 2011 at 2:11pm

Woot!  i just added into the whole definition and that works!

 

Just so I understand what is going on,

1. you simplified the tree of curves
2. exploded them to get the points on the curves to test
3. I'm getting confused from here on out with the shifting of the lists -1 and the evaluate curve sliders that are feeding into the 2pt Vector components.
4. Then you are sorting the exploded segments and joining them back up using the analyzed point as the starting point.

Thank you sooooo much!

ryan

Permalink Reply by Danny Boyes on June 27, 2011 at 3:39pm

Just so you know

 

A Shift list with S=-1 W=False will remove the last point in a list.

A, B, C, D, E shift back one would become E, A, B, C, D. As the first and the last points of an exploded Polycurve are the same all this is doing is making the list unique.

 

The Point on curve component is enabling you to create a vector between the vertex point and a smidge along the curve. Where as the shift list -1 and point on the curve is getting a vecto between the vertex point and a smidge along the previous curve. Thus creating and angle at the vertex to compare with all the others.