Closed kfunaoka closed 6 years ago
Fixed at Commit 0688f39
The waypoint loader again doesn't work in QuickStart. I'm following the video here https://www.youtube.com/watch?v=OWwtr_71cqI
Using v1.10, running in docker. All prior processes work, but running the my_mission_planning.launch script, it errors with:
[config_waypoint_loader_rostopic-4] process has died [pid 14291, exit code 1, cmd /opt/ros/kinetic/lib/rostopic/rostopic pub -l /config/waypoint_loader autoware_msgs/ConfigWaypointLoader {multi_lane_csv: /home/autoware/.autoware/data/path/moriyama_path.txt, replanning_mode: false, velocity_max: 20.0, velocity_min: 4.0, accel_limit: 0.98, decel_limit: 0.98, radius_thresh: 20.0, radius_min: 6.0, resample_mode: true, resample_interval: 1.0, velocity_offset: 4, end_point_offset: 5} __name:=config_waypoint_loader_rostopic __log:=/home/autoware/.ros/log/9f0af6d2-358f-11e9-ad77-9cb6d0fc87d3/config_waypoint_loader_rostopic-4.log]. log file: /home/autoware/.ros/log/9f0af6d2-358f-11e9-ad77-9cb6d0fc87d3/config_waypoint_loader_rostopic-4*.log
And the log is empty. The referenced file moriyama_path.txt exists.
Thanks for your help!
Bug
waypoint_loader doesn't work from Quick Start even if my_launch for the moriyama sample is fixed.
Expected Behavior
waypoint is displayed.
Actual Behavior
waypoint is not displayed.
Steps to Reproduce the Problem
Apply patch to the files generated by my_launch.sh
@@ -60,12 +60,12 @@
diff --git a/my_sensing.launch b/my_sensing.launch index 9cb948f..205b847 100644 --- a/my_sensing.launch +++ b/my_sensing.launch @@ -13,7 +13,7 @@
Specifications