[JTC] Reject trajectories with nonzero terminal velocity#567
Conversation
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## master #567 +/- ##
==========================================
- Coverage 35.78% 32.48% -3.31%
==========================================
Files 189 7 -182
Lines 17570 665 -16905
Branches 11592 357 -11235
==========================================
- Hits 6287 216 -6071
+ Misses 994 157 -837
+ Partials 10289 292 -9997
Flags with carried forward coverage won't be shown. Click here to find out more.
|
I don't agree with this at all. If we have velocity only input, we want to continue moving between trajectories. This is not so unusual scenario, e.g., when we have joystick input. I would rather like to see a timeout if we have velocity-only input to stop the input. |
|
Ok, I did not think of using JTC with Joystick, but rejecting it always did not seem to make sense for me too. |
Exactly, I think we want to avoid run away if only velocity is used. |
|
now I'm confused :D maybe we should discuss this in the next WG meeting |
|
any update merging this PR? |
|
@BarisYazici you could help out by reviewing #558 and this PR. I think everyone can do this without special permissions (goto Files changed -> Review Changes on top right corner) |
|
I've split this PR into two, the more important one is #608 |
@christophfroehlich in which order should this be merged? |
|
the order listed in #607 would be fine |
|
This pull request is in conflict. Could you fix it @christophfroehlich? |
1 similar comment
|
This pull request is in conflict. Could you fix it @christophfroehlich? |
a78da5a to
cba9ce3
Compare
|
The failing test is not related to this PR, but shows the flakiness of the JTC tests 😕 |
joint_trajectory_controller/src/joint_trajectory_controller_parameters.yaml
Outdated
Show resolved
Hide resolved
…s#567) * Reject receiving trajectory of last velocity point is non-zero * Update docs * Add tests * Change to parameterized test * Rename parameter * not true -> false --------- Co-authored-by: Bence Magyar <bence.magyar.robotics@gmail.com>
…s#567) * Reject receiving trajectory of last velocity point is non-zero * Update docs * Add tests * Change to parameterized test * Rename parameter * not true -> false --------- Co-authored-by: Bence Magyar <bence.magyar.robotics@gmail.com>
* Reject receiving trajectory of last velocity point is non-zero * Update docs * Add tests * Change to parameterized test * Rename parameter * not true -> false --------- Co-authored-by: Bence Magyar <bence.magyar.robotics@gmail.com>
* Reject receiving trajectory of last velocity point is non-zero * Update docs * Add tests * Change to parameterized test * Rename parameter * not true -> false --------- Co-authored-by: Bence Magyar <bence.magyar.robotics@gmail.com> (cherry picked from commit 99b67d7)
* Reject receiving trajectory of last velocity point is non-zero * Update docs * Add tests * Change to parameterized test * Rename parameter * not true -> false --------- Co-authored-by: Bence Magyar <bence.magyar.robotics@gmail.com> (cherry picked from commit 99b67d7)
As suggested by @bmagyar, the new trajectory should be even ignored if the last velocity point is nonzero.
allow_nonzero_velocity_stop==true.I also added a test for that, please review #603 first.