New ghPython with Node-in-Code™ and Multi-threading

Replies to This Discussion

Permalink Reply by Arturs Tols on December 23, 2013 at 5:00am

Works great, thanks!

I had no idea I had to do that. Are there any sources I could read to get to know more about python scripting in Rhino?

Cheers

Permalink Reply by djordje on December 23, 2013 at 5:10am

Yes, there are but mostly related to scripting in Rhino Python Editor.
Check the Rhino Python primer and tutorials from Mcneel's wiki website.

Permalink Reply by Arturs Tols on December 23, 2013 at 6:47am

Here I am again,

I'm sorry I'm hijacking the thread to solve this, but it really seems bizarre as I can't explain what's going on. The line I generate inside the python script seems fine but it doesn't generate any output compared to a line I supply in the inputs?? Is there some generic typecast I am missing?

Permalink Reply by djordje on December 23, 2013 at 7:37am

Hi Arturs,

You are using a rhinoscriptsyntax function AddLine() to generate your line. This function returns a guid (an object identifier), whereas your ghpythonlib.component function EvaluateLength requires curve object, as it's first argument. Take a look at this discussion, somewhat similar questions appeared there.
So what needs to be done is to feed the guid of your _line curve into the rs.coercecurve() function, in order to create a curve object. Then feed that into ghcomp.EvaluateCurve:

import rhinoscriptsyntax as rs
import scriptcontext
import ghpythonlib.components as ghcomp

_line = rs.AddLine(y,z)
line_object = rs.coercecurve(_line)

b = ghcomp.EvaluateLength(u,0.5).point

a = _line

c = ghcomp.EvaluateLength(line_object,0.3).point

You can also try not to puzzle yourself whether you are supplying guid or an object, by simply using a ghcomp function for creating a line, instead of rhinoscriptsyntax AddLine one:

import rhinoscriptsyntax as rs
import scriptcontext
import ghpythonlib.components as ghcomp

_line = ghcomp.Line(y,z)

b = ghcomp.EvaluateLength(u,0.5).point

a = _line

c = ghcomp.EvaluateLength(_line,0.3).point

Please attach your files for future questions.

Permalink Reply by Arturs Tols on December 23, 2013 at 8:00am

Awesome, thank you.
It's not easy to find tutorials on this subject as google mostly churns out info on python in general.

Have a great holiday, djordje!

Permalink Reply by djordje on December 23, 2013 at 8:22am

Agree with that. There should be an error message, that supplied data is not of a required type.

@ Arturs Tols:
Thank you. You too.

Permalink Reply by Rasmus Holst on January 10, 2014 at 7:18am

I don't know if this is the place to post this. I am very exited about this new functions. But I recently noticed that the gh.SurfaceClosestPt seems to be working a lot slower than by using rhinoscriptsyntax, where one has to use 3 commands if you want to get the point and the distance.

(That's how I do it any way - rs.SurfaceClosestPoint - rs.EvaluateSurface - rs.Distance)

There might be a really good explanation, but I was just wondering if it might be a bug?

Permalink Reply by stevedemicoli on November 9, 2015 at 2:32pm

Hi there,

I am trying to use the "Group Points by distance" command with ghpython.
The ghcomp.PointGroups manages to order the list of points I am feeding it, however it does not create sub-lists (branches) for each group.

In the image below, the panel on the left is from the ghcomp script, while on the right it is using standard gh components. I would like to do this within ghpython if possible. As the image displays, the script is working well, however I need to have nested lists in order to make any use of the command.

Any advice would be greatly appreciated!

I have also posted this same question on the Rhino Forum.

• ‹ Previous
• 1
• 2
• 3
• Next ›
• Page