@rjoomen and @rjoomen This should solve or provide the necessary functionality to solve the issue where you do not want trajectories to accumulate. You have two option available. The first is to update the ros plugin to set the clear_namespace on the JointTrajectoryAdd event. The second, is to make sure to send the trajectory each time with the same UUID. In the case of the online planner example the same UUID approach should be sufficient. We could also generate say 10 UUID's and then cycle through them so you at least see a few iteration of the planner.
@rjoomen and @rjoomen This should solve or provide the necessary functionality to solve the issue where you do not want trajectories to accumulate. You have two option available. The first is to update the ros plugin to set the clear_namespace on the JointTrajectoryAdd event. The second, is to make sure to send the trajectory each time with the same UUID. In the case of the online planner example the same UUID approach should be sufficient. We could also generate say 10 UUID's and then cycle through them so you at least see a few iteration of the planner.