Skip to content

DOCS-3603: Fix get_pose example #861

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 6, 2025
Merged

DOCS-3603: Fix get_pose example #861

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/viam/services/motion/motion.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ async def move(
technique allows for planning and moving the frame itself to the ``destination``. To do so, simply create a resource name with
originating ReferenceFrame's name. Then pass in the resource name into ``component_name``. Ex::

resource_name = Arm.get_resource_name("externalFrame")
resource_name = Gripper.get_resource_name("externalFrame")
success = await MotionServiceClient.move(resource_name, ...)

::
Expand Down Expand Up @@ -347,11 +347,11 @@ async def get_pose(

::

# Note that the example uses the ``Arm`` class, but any component class that inherits from ``ComponentBase`` will work
# (``Base``, ``Gripper``, etc).
# Note that the example uses the ``Gripper`` class, but any component class that inherits from ``ComponentBase`` will work
# (``Arm``, ``Base``, etc).

# Create a `component_name`:
component_name = Arm.get_resource_name("arm")
component_name = Gripper.get_resource_name("my_gripper")

from viam.components.gripper import Gripper
from viam.services.motion import MotionClient
Expand Down