Skip to content

the value of planning_horizon and rog map size #15

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

Open
fractal1z opened this issue Apr 12, 2025 · 2 comments
Open

the value of planning_horizon and rog map size #15

fractal1z opened this issue Apr 12, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@fractal1z
Copy link

planning_horizon: 7.0
planning_horizon: This parameter controls the planned length of the trajectory, when I reduce map_size: [50,50,6] to map_size: [10,10,6] (x, y, less than twice planning_horizon) the trajectory will be unplanned or severely deformed and twisted

@KLMN2001
Copy link

I also experienced this problem, I tried to test it on a real machine, when the speed was low (e.g. v_x = 1.0) , my planning_horizon and receding_dis were set to low accordingly, by subscribing to“/planning/pos_cmd” to get the trajectory, some parts of the trajectory will overlap and the overall look is not very smooth, looking forward to your response!

Image

Image

@RENyunfan
Copy link
Collaborator

Dear all,

It seems we have a significant issue to address. I am currently occupied with some impending deadlines, but I will do my best to find time this week to reproduce the problem and work on a solution.

Thank you.

@RENyunfan RENyunfan added the bug Something isn't working label Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants