velocity_control: allow non-persistent initial velocity commands #2265
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.
🎉 New feature
Specify non-persistent initial velocity
Summary
Currently the
velocity_control
system allows specifying initial velocities, but it treats them as persistent velocity commands. This adds a@persistent
attribute to the//initial_angular
and//initial_linear
plugin elements, which can be set to false in order to specify an initial velocity rather than a persistently updated velocity.This pull request builds upon #2228 and targets that branch. This is in draft mode until the example is well-documented and a test is added.
Test it
Run with the
examples/worlds/initial_velocity.sdf
example world and observe different behaviors with different values of the@persistent
attribute.Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.