-
Notifications
You must be signed in to change notification settings - Fork 52
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
Support odom topic #424
Support odom topic #424
Conversation
…to hrpsys-base trunk update at https://code.google.com/p/hrpsys-base/source/detail?r=1039 commit ;; we do not need to change usage of these methods
… according to hrpsys-base commit ;; https://code.google.com/p/hrpsys-base/source/detail?r=1040
…oBalancer_idl_update' into support-odom-imu-topic
Conflicts: hrpsys_ros_bridge/package.xml
@garaemon, if you could not wait for discussion start-jsk/hrpsys#75 and start-jsk/openhrp3#43, you can create branch at rtmros_common, for example devel or hrpsys_trunk and continue developping, As for hrpsys package, you just locally change https://github.com/start-jsk/hrpsys/blob/master/Makefile.hrpsys-base#L7 |
creating hrpsys trunk branch is a reasonable idea. Because in order to test trunk related codes on real robot, we need to @snozawa what do you think about it ? 2014年4月16日水曜日、Kei Okadanotifications@github.comさんは書きました:
from iPhone |
this PR includes following PRs by @snozawa: |
I think creating branch is reasonable, too. |
I don't understand all codes, but it seems this can be merged if you revert |
I will work on this PR to merge into master |
I will update this PR to remove changes included in #397 |
updated PR to #476 |
do not publish
/odom
tf frames but publish/odom
topic (nav_msgs/Odometory
).see #409 for more detail.
It required hrpsys trunk