Skip to content
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

Swiz/cartesian interpolation fix #1

Open
wants to merge 15 commits into
base: mwiz/bug_fixes
Choose a base branch
from

Conversation

swiz23
Copy link

@swiz23 swiz23 commented Oct 14, 2022

No description provided.

wyattrees and others added 15 commits June 23, 2022 14:05
…ting the goal so it does not block the server from accepting a cancel request. While client is waiting for the result future, repeatedly check if preempting was requested and send a cancel request if it was
The twist motion performs an angular rotation about the given axis _and_
the origin of ik_frame as well as a linear translation.
Both transforms are expressed w.r.t. the model frame and thus require
left-multiplication to ik_frame's current pose.
Fix handling of ik_frame in Cartesian path planning

The ik_frame should move in a straight-line Cartesian path.
However, so far the link frame was following a Cartesian path.
Fix getRobotTipForFrame()

When passing the root frame, getRigidlyConnectedParentLinkModel() returns
a nullptr for robot_link, causing a segfault.
Actually, we don't need to use that method at all. We just need to find
the robot_link of an associated body.
Rename variables in visualizePlan()

- link_pose -> start_pose
- pos_link -> pos_start
@mechwiz mechwiz force-pushed the mwiz/bug_fixes branch 2 times, most recently from adb0d55 to ddbe875 Compare January 4, 2023 00:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants