-
Notifications
You must be signed in to change notification settings - Fork 97
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
[fetcheus] override :move-to-wait to set :correction nil #1169
[fetcheus] override :move-to-wait to set :correction nil #1169
Conversation
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.
この書き方だと、robot-move-base-interfaceでは(send *ri* :move-to-wait :correction t or nil)
としてcorrectionをスキップするのに対して、
fetch-interfaceでは(send *ri* :move-to-wait 何もなし or :correction)
としてcorrectionをスキップすることになり、少しややこしいかなと思いました。
https://github.com/jsk-ros-pkg/jsk_pr2eus/pull/418/files#diff-15f6920b924513f6027d36b361f85bbdR1377
以下のようなプログラムではダメでしょうか?
robot-move-base-interfaceでは:correction
のデフォルト値がtだけど、fetch-interfaceではデフォルト値がnilになっているはず。
(:move-to-wait (&rest args &key (correction nil))
(send-super* :move-to-wait args :correction correction))
いや、fetch-interfaceも
|
山口君がいいたいのは、keyとrestの順序が逆なのかな
どっちでもいいんだけど、 |
あ、すいません。勘違いしてました。 |
upstream is merged |
|
4fec762
to
52591ee
Compare
waiting upstream jsk-ros-pkg/jsk_pr2eus#418this PR skip correction step in
:move-to
, which is not useful for Fetch robot.