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

How to define the drone footprint for collision free path planning? #17

Closed
Pallav1299 opened this issue Sep 24, 2021 · 4 comments
Closed

Comments

@Pallav1299
Copy link

Pallav1299 commented Sep 24, 2021

Thanks for the great work. Are we defining the drone footprint for collision free path planning in ego-planner-swarm? If yes, how? Is there any parameter for the same?
Do we have to configure the obstacle inflation to control the same?

In general, a brief documentation of the planner params would help a lot.

@bigsuperZZZX
Copy link
Member

Sorry, I don't quite understand your first sentence, what's the word "footprint" mean?

@Pallav1299
Copy link
Author

Sorry, I don't quite understand your first sentence, what's the word "footprint" mean?

@bigsuperZZZX, "footprint" refers to the robot_footprint from ROS navigation stack. This basically means the dimensions of the robot.
So to elaborate, how are we telling the planner about the robot dimensions? Is it considering a point model?
With the default planner configuration, I witnessed quite a lot of collisions in simulation tests.

Since I couldn't find a parameter for the robot_footprint, that's when I started comparing it to the ROS Navigation stack.
In order to reduce the collisions, I increased the obstacle inflation param in the advanced_param.xml, which I don't think is generally right to do. How do you define the robot dimensions to the planner?

@bigsuperZZZX
Copy link
Member

In fact, we use a point model and the obstacle inflation is the right way to define the "footprint".

@Pallav1299
Copy link
Author

@bigsuperZZZX, thanks for the answer.

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

2 participants