Add joint trajectory remove namespace event #131
Merged
Conversation
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
|
@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. |
Levi-Armstrong
deleted the
feature/joint-trajectory-remove-namespace-event
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.