Ask Your Question
0

[Autoware 1.12.0] astar_avoid can't correct closest waypoint in some cases

asked 2019-07-18 22:19:48 -0500

tony99090947@gmail.com gravatar image

Required information:

  • Operating system and version: Ubuntu 16.04
  • Autoware installation type: From source
  • Autoware version or commit hash: tag v.1.12
  • ROS distribution and version: Kinetic
  • ROS installation type: from binaries
  • Package or library, if applicable: N/A

Description of the bug

We plan path using way_palnner, waypoint_planner and waypoint_follower. After vehicle reached goal, astar will calculate incorrect closest waypoint if we want to plan new path

The error messages is:

no candidate. search closest waypoint from all waypoints...

no candidate. search closest waypoint from all waypoints...

no candidate. search closest waypoint from all waypoints...

[checkInitialized] initialized: 1

Please refer to below video, rosbag and ros log for how to reproduce this issue:

video: https://drive.google.com/open?id=1nCE...

rosbag: https://drive.google.com/open?id=1mal...

ros log: https://drive.google.com/open?id=1X6O...

Any response will be greatly appreciated! Many thanks for your help.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2019-08-29 16:15:23 -0500

Doug gravatar image

I'm also very curious about this. Did you find out what was the issue ? Thanks

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2019-07-18 22:19:48 -0500

Seen: 70 times

Last updated: Aug 29