I’ve searched but I couldn’t find my exact problem. All cards on the table, I’m a COMPLETE noob at GH.
What I want to do is create a sphere with the center at the sphere’s radius in plus Y. So the the “belly button” of the sphere is at 0,0,0.
This works perfect! I didn’t realize that the first sphere actually had nothing to do with the solution.
LOL, my “belly button” analogy was just trying (poorly) to describe the edge of the sphere on the origin (0,0,0)
“B” input of sphere component require a plane object.
We can create that plane with “XY Plane” that ask for a point object.
And we can create a point from XYZ coordinates.
Points and vectors, in grasshopper, can be swapped at any time, as they both are “a small triplet of numbers”!
Also, any component requiring a plane will accept a point and convert it to a world XY parallel plane with origin on that point.
So, by giving a vector to a component that require a plane it will happen 2 implicit conversions:
It’s easy to understand that a point instead of a plane will default to a ‘World XY’ plane at that point location. The vector conversion is less obvious. To me, it’s not just that both are “a small triplet of numbers” but a vector instead of a point can be considered as “move the origin point (0,0,0) with this vector and use the resulting point”. Same result, different point of view, no pun intended.
I’m OK with using points instead of located ‘World XY’ planes but not as cool about using vectors where points are expected. Seems more like a type or logic violation, though it obviously works fine. YMMV.