-
Notifications
You must be signed in to change notification settings - Fork 22
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.
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
Default wrist_tform_tool to identity #149
Conversation
Pull Request Test Coverage Report for Build 11731269410Details
💛 - Coveralls |
@@ -496,6 +496,10 @@ def hand_pose( | |||
|
|||
arm_cartesian_command = arm_command_pb2.ArmCartesianCommand.Request( | |||
root_frame_name=ref_frame, | |||
wrist_tform_tool=geometry_pb2.SE3Pose( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@llee-bdai Is this the function that you recently fixed? I am trying to figure out how much of a breaking change this is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that this function is called hand_pose
but really sets the pose of the arm, and also is called in the arm_pose_cmd_callback
of the SpotROS
node...
how would you feel about
- Renaming this to
set_arm_pose()
- Actually making this transform an argument of the function instead of hard-coding, but still defaulting it to identity?
- Making the above default arg an
SE3
and converting it to the protobuf inside this function body?
@scastro-bdai i am nervous that renaming from |
@amessing-bdai pulling you into comments here because wer're all talking about the same thing. To answer your question as to if this is the function I recently fixed, yes, in terms of fixing it by removing ROS1 dependencies and actually using it. This isn't a breaking change for anything internal, but it would be breaking externally, technically.
|
Hmm, since we recently changed the signature already it's probably ok to further change it, but lets make sure this is the last change to the signature and not make this common practice. |
I am also perfectly fine not changing the signature because it's been named this for a while and just very clearly specifying in the function comments that it's to the wr1 link |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC the offset that it defaults to is the offset from the wrist to the center of the gripper, which is usually the "tool frame" people want.
I think this is probably not a desirable change especially this deep in the code in a repo that lots of people use...
I guess as a compromise, should we include the optional offset argument, and default it to the "sanctioned" tool frame? |
If you want to be explicitly commanding the wr1 link, it might make sense to make a new function called something like |
I'm cool with @khughes-bdai suggestion of adding a whole new wrist pose function. But also, if we add another function, I wouldn't mind just adding in all the extra params required to specify wrist to some offset pose |
On second thought, because this change ends up affecting a lot more than I expected, I am going to close this. Thanks for all the comments |
Turns out
ArmCartesianCommand
defaultswrist_tform_tool
to be some approximately 20cm offset https://dev.bostondynamics.com/protos/bosdyn/api/proto_reference#armcartesiancommand-requestThis PR sets the transform to be identity so that when you send a hand pose, it's commanding the wrist to the pose, and not wrist plus some unknown defaulted offset.