-
Notifications
You must be signed in to change notification settings - Fork 935
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
Should get_current_state_bounded
be available in MoveGroupCommander, and why is it bounded?
#1966
Comments
I tried to implement this, but when I call
I get that error when I try to call the
|
I actually found this because I want to use get_current_state_bounded, and saw it wasn't fully implemented. Did you ever finish this? |
The Python API by far isn't complete. If you are missing something, please file a corresponding PR. |
…veit#2356) * implement get state and get state bounded * add enforceBounds Co-authored-by: Peter <pmitrano@storm20.04>
…veit#2356) * implement get state and get state bounded * add enforceBounds Co-authored-by: Peter <pmitrano@storm20.04>
* implement get state and get state bounded * add enforceBounds Co-authored-by: Peter <pmitrano@storm20.04>
I wanted to use
get_current_state
in Python and came across this. Can someone do a quick sanity check?This function
getCurrentStateBoundedPython
was introduced in the wrapper 4 years ago, but isn't used inmove_group.py
(link). I think this is an oversight.Also, why is it bounded? Since there is no equivalent in the C++ MoveGroupInterface, I am a little confused.
If there's no objections I would submit a PR to connect this function in
move_group.py
, and maybe make itget_current_state
instead ofget_current_state_bounded
, when I get around to it.The text was updated successfully, but these errors were encountered: