Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
New Tutorial on Time Parameterization / Speed Control (#50)
- Loading branch information
1 parent
e9e1816
commit c1e7120
Showing
2 changed files
with
25 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
Time Parameterization Tutorial | ||
============================== | ||
|
||
MoveIt! is currently primarily a *kinematic* motion planning framework - it plans for joint or end effector positions but not velocity or acceleration. However, MoveIt! does utilize *post*-processing to time parameterize kinematic trajectories for velocity and acceleration values. Below we explain the settings and components involved in this part of MoveIt!. | ||
|
||
Speed Control | ||
------------- | ||
|
||
From File | ||
^^^^^^^^^ | ||
|
||
By default MoveIt! sets the velocity and acceleration of a joint trajectory to the default allowed in the robot's URDF or ``joint_limits.yaml``. The ``joint_limits.yaml`` is generated from the Setup Assistant and is initially an exact copy of the values within the URDF. The user can then modify those values to be less than the original URDF values if special constraints are needed. Specific joint properties can be changed with the keys ``max_position, min_position, max_velocity, max_acceleration``. Joint limits can be turned on or off with the keys ``has_velocity_limits, has_acceleration_limits``. | ||
|
||
During Runtime | ||
^^^^^^^^^^^^^^ | ||
|
||
The speed of a parameterized kinematic trajectory can also be modified during runtime as a fraction of the max velocity and acceleration set in the configuration values, as a value between 0-1. To change the speed on a per-motion plan basis, you can set the two scaling factors as described in `MotionPlanRequest.msg <http://docs.ros.org/kinetic/api/moveit_msgs/html/msg/MotionPlanRequest.html>_`. Spinboxes for setting both of those factors are also available in the `MoveIt! MotionPlanning rviz plugin <ros_visualization/visualization_tutorial.html>_`. | ||
|
||
Time Parameterization Algorithms | ||
-------------------------------- | ||
|
||
MoveIt! can support different algorithms for post-processing a kinematic trajectory to add timestamps and velocity/acceleration values. Currently only one is available by default in MoveIt!: `Iterative Parabolic Time Parameterization <https://github.com/ros-planning/moveit/blob/kinetic-devel/moveit_core/trajectory_processing/src/iterative_time_parameterization.cpp>`. This algorithm is used by default in the `Motion Planning Pipeline <pr2_tutorials/planning/src/doc/planning_pipeline_tutorial.html>_` as a Planning Request Adaptor as documented in `this tutorial <pr2_tutorials/planning/src/doc/planning_pipeline_tutorial.html#using-a-planning-request-adapter>_`. | ||
|
||
Note that although the Iterative Parabolic Time Parameterization algorithm MoveIt! uses has been used by hundreds of robots over the years, there is a long outstanding `bug with it <https://github.com/ros-planning/moveit/issues/160>_` whose fix is a work in progress. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters