-
Notifications
You must be signed in to change notification settings - Fork 1k
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
description: spec limits in degrees. #533
description: spec limits in degrees. #533
Conversation
Use rosparam's and xacro's support for these special constructors to convert to radians on-the-fly.
This PR is expected to fail until ros/xacro#252 gets merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 thanks!
But I suggest to wait until the latest xacro package version is released
Yes, that's my intention. CI is failing for a different reason though: somehow it can't find |
b385f57
to
c31636b
Compare
|
I tested the simulation locally with the updated release version of the |
Thanks for the enthusiasm, but c31636b was actually not supposed to end up in the merge :) I'll fix it later. |
Ups sorry, I just showed that I had previously reviewed and approved the PR. I didn't scroll again the changed files. Let me know if you don't have time and I should delete the commit and rebase the branch. |
…limits description: spec limits in degrees.
…limits description: spec limits in degrees.
I've dropped the commit. Now that it's a 1 commit PR, it should've been squash-merged, but I've left your merge commit as-is. |
Both
rosparam
(wiki page) andxacro
(with ros/xacro#252 merged) support special yaml constructors which allow conversion of numeric values to radians on-the-fly.This makes it possible for us to specify joint limits in the
config/urXX/joint_limits.yaml
files in degrees, which are much more human readable and easier to compare to the spec sheets.