You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: joint_trajectory_controller/doc/trajectory.rst
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,6 +115,11 @@ Trajectory Replacement
115
115
116
116
Joint trajectory messages allow to specify the time at which a new trajectory should start executing by means of the header timestamp, where zero time (the default) means "start now".
117
117
118
+
.. warning::
119
+
120
+
As of now, this functionality is not ported to ROS 2, see `this issue <https://github.com/ros-controls/ros2_controllers/issues/84>`__ for more information.
121
+
The current implementation just forgets the old trajectory.
122
+
118
123
The arrival of a new trajectory command does not necessarily mean that the controller will completely discard the currently running trajectory and substitute it with the new one.
119
124
Rather, the controller will take the useful parts of both and combine them appropriately, yielding a smarter trajectory replacement strategy.
0 commit comments