-
Notifications
You must be signed in to change notification settings - Fork 545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow setting of minimal velocity #10
Comments
Hi @balamesh, in general, adding a lower bound on the minimum velocity should be possible. However, integrating this into the optimization scheme significantly increases complexity since we already support switching between forward and backwards motions (it might introduce non-smooth cost functions or even more local minima). In my opinion, adjusting the controls/velocities after obtaining the optimization result should work fine in many applications, e.g. using a simple three-point-controller before forwarding the velocities to the actual base controller:
However, the threshold
If It would be really straight forward to add those few lines to the |
Yes thanks a lot for your help. We managed to solve this by implementing a minimum velocity on the controller side. |
For the record, since it might be related: |
Hi,
is it possible to implement a minimal velocity? We are using the teb_local_planner with success on either simulated or real ackermann driven robots.
But in some cases we are facing the problem that the robot base cannot execute the desired velocity.
E.g. it would only start driving at a minimal velocity of 0.1 m/s.
Best regards and thumbs up for the great work!
The text was updated successfully, but these errors were encountered: