You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, when I look over the code, especially the <pickup_trajectory> function, I just notice that when picking up the optimum trajectory from the candidates, the cost function only considers the <direction difference, goal distance & difference between the consecutive trajectories>, no immediate obstacle distance. It should be fine for a static obstacle, but may fail dealing with the moving ones. Any suggestions or ideas to impove the performance of this planner in dymamic environment.
The text was updated successfully, but these errors were encountered:
Hi, when I look over the code, especially the <pickup_trajectory> function, I just notice that when picking up the optimum trajectory from the candidates, the cost function only considers the <direction difference, goal distance & difference between the consecutive trajectories>, no immediate obstacle distance. It should be fine for a static obstacle, but may fail dealing with the moving ones. Any suggestions or ideas to impove the performance of this planner in dymamic environment.
The text was updated successfully, but these errors were encountered: