Difference between revisions of "Navigation Tuning"
From wikidb
(→Odometry (1.2)) |
(→meter_scoring) |
||
| Line 7: | Line 7: | ||
== meter_scoring == | == meter_scoring == | ||
| − | [ WARN] [1478392084.188946161]: Trajectory Rollout planner initialized with param meter_scoring not set. Set it to true to make your settins robust against changes of costmap resolution. | + | [ WARN] [1478392084.188946161]: Trajectory Rollout planner initialized with param meter_scoring not set. |
| + | Set it to true to make your settins robust against changes of costmap resolution. | ||
Add the following to base_local_planner_params.yaml. | Add the following to base_local_planner_params.yaml. | ||
meter_scoring: true | meter_scoring: true | ||
| − | + | ||
= Odometry (1.2) = | = Odometry (1.2) = | ||
Revision as of 21:10, 6 November 2016
References
- Navigation Tuning Guide
- ROS Navigation Tuning Guide by Kaiyu Zheng student at University of Washington.
Removing Warning Messages
meter_scoring
[ WARN] [1478392084.188946161]: Trajectory Rollout planner initialized with param meter_scoring not set.
Set it to true to make your settins robust against changes of costmap resolution.
Add the following to base_local_planner_params.yaml.
meter_scoring: true
Odometry (1.2)
Run
Terminal 1
roscore
Terminal 2
roslaunch floor_hugger keyboard_teleop.launch
Terminal 3
roslaunch floor_hugger active_mapping.launch
Used "d" to rotate the Floor Hugger slowly clockwise. The following is after four or more rotations. Edges look well defined.
