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

Fix bug in cartesian planning #68

Merged
merged 1 commit into from
May 10, 2024
Merged
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions pymoveit2/moveit2.py
Original file line number Diff line number Diff line change
Expand Up @@ -1936,11 +1936,11 @@ def _plan_cartesian_path(
)

# The below attributes were introduced in Iron and do not exist in Humble.
if hasattr(__cartesian_path_request, "max_velocity_scaling_factor"):
if hasattr(self.__cartesian_path_request, "max_velocity_scaling_factor"):
self.__cartesian_path_request.max_velocity_scaling_factor = (
self.__move_action_goal.request.max_velocity_scaling_factor
)
if hasattr(__cartesian_path_request, "max_acceleration_scaling_factor"):
if hasattr(self.__cartesian_path_request, "max_acceleration_scaling_factor"):
self.__cartesian_path_request.max_acceleration_scaling_factor = (
self.__move_action_goal.request.max_acceleration_scaling_factor
)
Expand Down