Closed rayvburn closed 1 year ago
When robot is located a little further down the global plan, it produces local plan that crosses the forbidden area produced by a sharp corner:
After multiple tries with different costmap converter parameters, it seems that the only method to overcome this issue is to produce as many point obstacles as possible (here, cluster_min_pts
= 1, cluster_max_pts
= 2).
However, this produces massive computational cost and slows down planner a lot.
So, in a nutshell, trajectory generator is very sensitive to improper obstacle segmentation. This issue was previously addressed at #17.
After thorough debugging it seems that failures are caused by Social Force Model itself. Force grid visualization shown that robot is directed towards walls. As a remedy, another approach to trajectory generation is used ATM.
Related to both
costmap_converter
andhubero_local_planner
parameters