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
Reduced the minimum max velocity joint limit from 0.01 to 0.001 for totg #2937
Conversation
@grejj I think this is a good change but do we even need a minimum. It looks to me like throwing an error might be better like this:
|
Codecov Report
@@ Coverage Diff @@
## master #2937 +/- ##
==========================================
+ Coverage 61.73% 61.78% +0.05%
==========================================
Files 373 373
Lines 33425 33429 +4
==========================================
+ Hits 20632 20651 +19
+ Misses 12793 12778 -15
Continue to review full report at Codecov.
|
Thanks for creating the PR after our brief discussion on Discord! |
…ion failure if limits less than/equal to zero
LGTM. |
@grejj, please apply the suggested formatting changes. Ideally, install https://pre-commit.com to catch these at commit time. |
Congrats on getting your first MoveIt pull request merged and improving open source robotics! |
Description
Currently the minimum value you can specify for the the max velocity outputted for a joint during time optimal trajectory parameterization is 0.01 rad/s or m/s. For joints that are unable to move that fast and whose velocity limits are less than 0.01, the planned path outputted is unachievable with trajectory velocities being higher than the maximum velocity of the joint.
Reduced the value to 0.001.