-
Notifications
You must be signed in to change notification settings - Fork 181
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
industrial_utils: using 'default joint names' when parameter cannot be found is a bad idea #180
Labels
Comments
hi, is this as straightforward as raising as error and returning? |
@Ridhwanluthra: yes, it should fail:
a suitable message printed using |
cool, fixing this as a part of #wrid18 |
Ridhwanluthra
pushed a commit
to Ridhwanluthra/industrial_core
that referenced
this issue
Jul 11, 2018
Ridhwanluthra
pushed a commit
to Ridhwanluthra/industrial_core
that referenced
this issue
Jul 11, 2018
PR #195 has been merged closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In
industrial_utils/param_utils::getJointNames(..)
:industrial_core/industrial_utils/src/param_utils.cpp
Lines 122 to 129 in 9a0fe17
If either
controller_joint_names
cannot be found, or the urdf cannot be parsed for joint names,getJointNames(..)
returns a set of 'default names'.This is not a good behaviour: the function should fail if it cannot find any joint names. Making some names up (even though they follow ros-i conventions) and then returning successfully makes for poor reproducibility and complicates debugging.
The text was updated successfully, but these errors were encountered: