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
Select time parametrization algorithm in retime_trajectory #1508
Select time parametrization algorithm in retime_trajectory #1508
Conversation
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.
Please address the feedback.
I believe we need to make the time parametrization configurable for every place it might be called, so cleaning this up would be more involved...
moveit_ros/planning_interface/move_group_interface/src/wrap_python_move_group.cpp
Outdated
Show resolved
Hide resolved
moveit_ros/planning_interface/move_group_interface/src/wrap_python_move_group.cpp
Outdated
Show resolved
Hide resolved
moveit_ros/planning_interface/move_group_interface/src/wrap_python_move_group.cpp
Outdated
Show resolved
Hide resolved
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.
Thank you for these changes.
Could you please add a simplistic unit test files that runs all types of time parametrization?
39f8d8a
to
2c7bb2c
Compare
…time_trajectory in pyhon interface of move_group.
94c9ce4
to
ee64e63
Compare
Congrats on getting your first MoveIt! pull request merged and improving open source robotics! |
* Python wrapper: add acceleration_scaling_factor argument to retime_trajectory. * wrap_python_move_group.cpp, move_group.py: add algorithm option to retime_trajectory in pyhon interface of move_group. * moveit_commander: add python_time_parameterization test.
* Python wrapper: add acceleration_scaling_factor argument to retime_trajectory. * wrap_python_move_group.cpp, move_group.py: add algorithm option to retime_trajectory in pyhon interface of move_group. * moveit_commander: add python_time_parameterization test.
@@ -489,7 +491,8 @@ class MoveGroupInterfaceWrapper : protected py_bindings_tools::ROScppInitializer | |||
} | |||
|
|||
std::string retimeTrajectory(const std::string& ref_state_str, const std::string& traj_str, | |||
double velocity_scaling_factor) | |||
double velocity_scaling_factor, double acceleration_scaling_factor, | |||
std::string algorithm) |
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.
This has caused a Travis breakage on master, it looks like it got through because this was committed to melodic first, then cherry-picked?
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.
Fix: #1589
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.
Thank you. Sorry for the inconvenience.
Description
Enable to select Time Parametrization Algorithm via
algorithm
argument inretime_trajectory
method of Python MoveGroupCommander.Ref: Time Parametrization Algorithms:
http://docs.ros.org/melodic/api/moveit_tutorials/html/doc/time_parameterization/time_parameterization_tutorial.html#time-parameterization-algorithms
Example use case:
https://github.com/mmurooka/moveit_tutorials/blob/time-parametrization-tutorial-master/demo_rs007n/scripts/demo_adept_motion_rs007n.py#L93-L102
(This PR contains #1506 .)
Checklist