Skip to content
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

navigation の精度改善策 #79

Closed
yasu80 opened this issue Sep 13, 2017 · 7 comments
Closed

navigation の精度改善策 #79

yasu80 opened this issue Sep 13, 2017 · 7 comments
Assignees

Comments

@yasu80
Copy link
Member

yasu80 commented Sep 13, 2017

実験はGazebo上, 実機の両方で行い, 問題点を洗い出すものとする

参考 : http://blog-sk.com/myrobo/ros/ros-move_base/

costmap

  • なるだけ raytrace range を広く取る

    • amclに多くのデータが渡り, 発散を防ぐ
    • 早期にマッピングを進める
  • infration radius/ max_vel_x , acc_lim_x と update_frequensy の相関をいい感じにする

    • 「手遅れ」になっている. 衝突コースに入っているにもかかわらず, infration_radius 内に入り, 評価が始まってから停止・モード変更に必要な時間がない
@yasu80
Copy link
Member Author

yasu80 commented Oct 15, 2017

いい文献です

http://kaiyuzheng.me/documents/navguide.pdf

@yasu80
Copy link
Member Author

yasu80 commented Oct 15, 2017

ここで直面しているのは

How to tune sim time
の項目では?

@yasu80
Copy link
Member Author

yasu80 commented Oct 15, 2017

http://wiki.ros.org/base_local_planner
の 4.2.4項
meter_scaringもtureにしたい

@yasu80
Copy link
Member Author

yasu80 commented Oct 15, 2017

@tanacchi の提案:
base_footprint の修正, 車軸とx軸を合わせる

@yasu80
Copy link
Member Author

yasu80 commented Oct 16, 2017

@tanacchi の指摘,
base_footprint が間違ってる(順番が)

@yasu80
Copy link
Member Author

yasu80 commented Oct 26, 2017

#97 も参照

@yasu80
Copy link
Member Author

yasu80 commented Nov 23, 2017

指針が決まったので閉じます

@yasu80 yasu80 closed this as completed Nov 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants