Three GhPython questions, based on the desire to stay in ghdoc context avoiding to have to “bake” as long as possible. The things below (except for reading the sphere radius) I can do by baking into Rhino, and then use “plain RhinoCommon” functions, but as said, exactly that (baking) is what I would like to avoid since it’s “too early” to bake in the middle of a long GH process, (I will have to update very often) :
Q1: Is it possible to create a GH Sphere based on GH (non-baked) fit points similar to the following RhinoCommon command :
It seems that Python has not implemented that variant of the Sphere command, but if there’s a way to tweak gh somehow, please let me know.
Q2: An option for Q1 exist, based on a GH component (Sphere Fit (
SFit)) that can create a sphere from FitPoints (and I’m already creating the points in a GhPython Script component), but, how can I feed this SFit component from a GhPython Script component with the points without baking them into Rhino? (it’s too time consuming to create & bake so many points).
Q3: When I do have a GH reference to a Sphere in my GhPython code, how can I retrieve the radius of the Sphere? Also this sphere property seems to be missing in GhPython. Any workaround?