autome

Hi, Is there any update on it. I am getting same error building on jetson docker. Thanks!

HI @jwallace42 This error is very repeatable and occurs every time when a current navigation is cancelled and next goal is difficult or non-navigable (very close to obstacle). It is...

Yeah, that is what I think. I didn't saw this error with other planners. I will try again tomorrow to check with others (smac Hybrid-A* Planner and Navfn)

Hi @jwallace42 This time I used publicly available [Amazon warehouse](https://github.com/aws-robotics/aws-robomaker-small-warehouse-world) with gazebo. Here are the results: - SMAC Lattice + RPP :: `Leads to error` - SMAC Lattice + DWB...

Here is the output from cancelling to reaching wrong (previous) goal. ``` [component_container_isolated-2] [INFO] [1659604458.696972564] [controller_server]: Goal was canceled. Stopping the robot. [component_container_isolated-2] [WARN] [1659604458.697013723] [controller_server]: [follow_path] [ActionServer] Client requested...

Yeah. I think the same too. I will try to check with other xmls next week.

Hi, I tried [navigate_through_poses_w_replanning_and_recovery.xml](https://github.com/ros-planning/navigation2/blob/main/nav2_bt_navigator/behavior_trees/navigate_through_poses_w_replanning_and_recovery.xml). As expected, this behaviour does not occur.

No problem. It's actually 1 week summer holiday next week here in Japan, so I will be out of office! Take your time!

@jwallace42 @SteveMacenski @padhupradheep Thank you everyone. The mentioned pr solves my issue. Tested on same gazebo environment. Sorry for the wait.

Maybe its better to just skip the in-place rotation poses with same (x,y) [while keeping the first and the last of those consecutive pose] in the cusp detection loop. Best...