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

Whether the current code can handle the dynamic objects? #28

Open
lukewenMX opened this issue Jun 6, 2022 · 0 comments
Open

Whether the current code can handle the dynamic objects? #28

lukewenMX opened this issue Jun 6, 2022 · 0 comments

Comments

@lukewenMX
Copy link

lukewenMX commented Jun 6, 2022

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.

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

1 participant