From 8efc78da3623823de449300ec136ddececef7ce8 Mon Sep 17 00:00:00 2001 From: JessamyT Date: Wed, 5 Mar 2025 22:11:07 -0800 Subject: [PATCH] DOCS-3603: Fix get_pose example --- src/viam/services/motion/motion.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/viam/services/motion/motion.py b/src/viam/services/motion/motion.py index dc33a2f6c..c6b6138c4 100644 --- a/src/viam/services/motion/motion.py +++ b/src/viam/services/motion/motion.py @@ -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, ...) :: @@ -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