ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A answers.ros.org

# Revision history [back]

The navigation stack is huge, so hundreds of parameters need to be tuned to you specific situation. It is impossible to help you without a very detailed description of your setup. However, there is a guideline on common mistakes and assumptions to check.

The navigation stack is huge, so hundreds of parameters need to be tuned to you your specific situation. It is impossible to help you without a very detailed description of your setup. However, there is a guideline on common mistakes and assumptions to check.

The navigation stack is huge, so hundreds of parameters need to be tuned to your specific situation. It is impossible to help you without a very detailed description of your setup. However, there is a guideline on common mistakes and assumptions to check.

The most obvious thing to me would be to check if the clearing parameter in your costmap observation sensor config (usually costmap_common_params.yaml) is set to true. If you use a VoxelGrid for obstacles, visualize the voxels and raytrace endpoints in RViz for any hints on what is going wrong.

The navigation stack is huge, so hundreds of parameters need to be tuned to your specific situation. It is impossible to help you without a very detailed description of your setup. However, there is a guideline on common mistakes and assumptions to check.

The most obvious thing to me would be to check if the clearing parameter in your costmap observation sensor config (usually costmap_common_params.yaml) is set to true. true anf if raytrace_range is big enough. If you use a VoxelGrid for obstacles, visualize the voxels and raytrace endpoints in RViz for any hints on what is going wrong.