[Autoware 1.12.0] astar_avoid can't correct closest waypoint in some cases
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 waypalnner, waypointplanner 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=1nCEVssqTMekfY5bYMEZ7OusrXMGp6HQb
rosbag: https://drive.google.com/open?id=1maliDyLwn4HbkPMyzRcRGHtveh0X_NNk
ros log: https://drive.google.com/open?id=1X6OJm7Vut2IVYCUeXlVphyU8N0wjoNWP
Any response will be greatly appreciated! Many thanks for your help.
Asked by tony99090947@gmail.com on 2019-07-18 22:19:48 UTC
Answers
I'm also very curious about this. Did you find out what was the issue ? Thanks
Asked by Doug on 2019-08-29 16:15:23 UTC
Comments