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

NavFn plans paths which brush obstacles when in tight spaces. #26

Closed
hershwg opened this issue Apr 4, 2013 · 0 comments
Closed

NavFn plans paths which brush obstacles when in tight spaces. #26

hershwg opened this issue Apr 4, 2013 · 0 comments

Comments

@hershwg
Copy link
Contributor

hershwg commented Apr 4, 2013

For instance, going through a 1 meter wide hallway with a 50 cm wide robot, the path should ideally go right down the center. As it is, the planned path will have the robot brush the near corner of the hall when entering and exiting, and potentially just slide right along the edge the whole way down the hall.

The incoming costmap has a sufficient inflation radius and cost function which falls off appropriately from obstacles, but inside NavFn::setCostmap() those cost values are rescaled per the needs of NavFn.

The problem is that the rescaling does not spread the input values nicely over the output range, it concentrates them at the max value. Therefore you get a wide plateau of high cost values around obstacles. In open environments with few obstacles, this is fine because it stays away from the plateau. In crowded environments, all the free map cells have equal costs on this plateau, so the planner just does strict shortest-path in this area.

@hershwg hershwg closed this as completed in 6697bb0 Apr 4, 2013
hershwg added a commit that referenced this issue Apr 4, 2013
This commit is low priority, it is just all the debugging infrastructure I used when
researching the fix for #26.  It doesn't change anything for normal operation.
nlimpert pushed a commit to nlimpert/navigation that referenced this issue Feb 25, 2020
…_vel stamp. As now time is always zero, isMoving always returns false
nlimpert pushed a commit to nlimpert/navigation that referenced this issue Feb 25, 2020
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