Comment by spiritninja for Make sure you have set in...
@Jordan Yeah you're right about the parameter. In-fact i had taken care of that earlier by changing the default value that's `True` to `False`. But the problem still persists and that is waht intrigued...
View ArticleComment by jordan for Make sure you have set in...
Check this... https://answers.ros.org/question/215538/allow_unknown-parameter-ignored/ The above may solve your issue. Robots around here use: `planner_frequency: 1.0` (in move_base_params.yaml), which...
View ArticleComment by spiritninja for Make sure you have set in...
Exactly. This is what I was trying out the other day after checking about the global planner [Here](http://wiki.ros.org/global_planner) on the Wiki page....
View ArticleComment by jordan for Make sure you have set in...
Please attach the entire modified 'costmap_common_params.yaml'.
View ArticleComment by drtritm for Make sure you have set in...
@spiritninja did you find the solution, I faced the same problem, even change allow_unknown or tracking_unknown_space
View ArticleComment by li9i for Make sure you have set in...
I was also frustrated with this issue. For future reference see https://github.com/ros-planning/navigation/issues/261#issuecomment-885545451
View ArticleAnswer by jordan for could someone explain why sometines the global path...
Make sure you have set in `navfn_global_planner_params.yaml`: allow_unknown: false #Specifies whether or not to allow navfn to create plans that traverse unknown space, default true I have observed...
View ArticlePath planned through unmapped region for goal present inside map.
could someone explain why sometines the global path planned by the robot for navigation ventures into the unmapped region? Images of the path planned to the goal are attached below. The planned path is...
View Article