Planning Simulation: failed to generate_valid_path in Pull out and pull over scenario

[a-strong-python]

Checklist

• I've read the contribution guidelines.
• I've searched other issues and no duplicate issues were found.
• I'm convinced that this is not my fault but a bug.

Description

While following the tutorial at https://autowarefoundation.github.io/autoware-documentation/main/tutorials/ad-hoc-simulation/planning-simulation/#pull-out-and-pull-over-scenario for the Pull out and pull over scenario, I encountered a failed to generate_valid_path error. I attempted multiple times but was unable to generate a valid path for pulling out. The first two examples—Lane driving scenario and Parking scenario—were executed successfully.

The command I used was:
./docker/run.sh --map-path ~/autoware_map --data-path ~/autoware_data ros2 launch autoware_launch planning_simulator.launch.xml map_path:=/autoware_map/sample-map-planning vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit

Error screenshots and partial logs are provided below:

[component_container_mt-40] [INFO] [1759039205.925464016] [control.autonomous_emergency_braking]: [AEB] waiting for control predicted trajectory
[rviz2-46] [INFO] [1759039206.285151980] [rviz2]: Setting goal pose: Frame:map, Position(3738.2, 73678.6, 0), Orientation(0, 0, -0.971081, 0.23875) = Angle: -2.65944
[component_container_mt-28] [INFO] [1759039206.658392911] [route_handler]: getMainLanelets: lanelet_sequence = [ids: 9232 ]
[component_container_mt-28] [INFO] [1759039206.658951103] [planning.mission_planning.mission_planner]: initial pose - x: 3775.826416, y: 73695.468750, z: 19.568000
[component_container_mt-28] [INFO] [1759039206.658981540] [planning.mission_planning.mission_planner]: initial orientation - qx: -0.001443, qy: -0.000353, qz: -0.971364, qw: 0.237593
[component_container_mt-28] [INFO] [1759039206.658993215] [planning.mission_planning.mission_planner]: goal pose - x: 3738.196777, y: 73678.617188, z: 0.000000
[component_container_mt-28] [INFO] [1759039206.659003180] [planning.mission_planning.mission_planner]: goal orientation - qx: 0.000000, qy: 0.000000, qz: -0.971081, qw: 0.238750
[component_container_mt-40] [INFO] [1759039206.714037645] [control.trajectory_follower.lane_departure_checker_node]: waiting for reference_trajectory msg...
[autoware_topic_state_monitor_node-11] [INFO] [1759039206.759428423] [system.topic_state_monitor_scenario_planning_trajectory]: /planning/scenario_planning/trajectory has not received. Set ERROR in diagnostics.
[component_container_mt-42] [INFO] [1759039206.774631976] [adapi.node.autoware_state]: AutowareState: WaitingForRoute => Planning
[autoware_topic_state_monitor_node-12] [INFO] [1759039206.838084609] [system.topic_state_monitor_trajectory_follower_control_cmd]: /control/trajectory_follower/control_cmd has not received. Set ERROR in diagnostics.
[autoware_topic_state_monitor_node-13] [INFO] [1759039206.984399155] [system.topic_state_monitor_control_command_control_cmd]: /control/command/control_cmd has not received. Set ERROR in diagnostics.
[component_container_mt-39] [WARN] [1759039207.045241503] [control.autoware_operation_mode_transition_manager]: Subscribed trajectory is timed out.
[component_container_mt-33] [WARN] [1759039207.114778335] [route_handler]: setMap() for invalid version map: 
[component_container_mt-33] [WARN] [1759039207.189606347] [behavior_path_planner.path_shifter]: Acc limit is too small to be applied. Tj: -0.533890, Ta: 4.780854, j: -0.280957, a_max: 0.343136, acc_limit: 0.150000
[component_container_mt-33] [WARN] [1759039207.221273549] [planning.scenario_planning.lane_driving.behavior_planning.behavior_path_planner.start_planner]: Not found safe pull out path, publish stop path
[component_container_mt-33] [WARN] [1759039207.223625185] [planning.scenario_planning.lane_driving.behavior_planning.behavior_path_planner.goal_planner]:  [pull_over] postProcess() is called without valid context_data. use dummy context data.
[component_container_mt-33] [WARN] [1759039207.305994912] [route_handler]: setMap() for invalid version map: 
[component_container_mt-33] [WARN] [1759039207.433593148] [planning.scenario_planning.lane_driving.behavior_planning.behavior_path_planner.RTCInterface[start_planner]]: [updateCooperateStatus] uuid : 65e665ef19723cdd15b6fb20b5bb33de cannot transit from RUNNING to WAITING_FOR_EXECUTION
[component_container_mt-33] 
[component_container_mt-33] [WARN] [1759039207.524523398] [planning.scenario_planning.lane_driving.behavior_planning.behavior_path_planner.RTCInterface[start_planner]]: [updateCooperateStatus] uuid : 65e665ef19723cdd15b6fb20b5bb33de cannot transit from RUNNING to WAITING_FOR_EXECUTION
[component_container_mt-33] 
[component_container_mt-34] [WARN] [1759039207.609096569] [route_handler]: setMap() for invalid version map: 
[component_container_mt-33] [WARN] [1759039207.623813177] [planning.scenario_planning.lane_driving.behavior_planning.behavior_path_planner.RTCInterface[start_planner]]: [updateCooperateStatus] uuid : 65e665ef19723cdd15b6fb20b5bb33de cannot transit from RUNNING to WAITING_FOR_EXECUTION
[component_container_mt-33] 
[component_container_mt-39] [INFO] [1759039207.673046004] [control.trajectory_follower.controller_node_exe]: Waiting for trajectory data
[component_container_mt-39] [INFO] [1759039207.673141248] [control.trajectory_follower.controller_node_exe]: Control is skipped since input data is not ready.
[component_container_mt-33] [WARN] [1759039207.723677120] [planning.scenario_planning.lane_driving.behavior_planning.behavior_path_planner.RTCInterface[start_planner]]: [updateCooperateStatus] uuid : 65e665ef19723cdd15b6fb20b5bb33de cannot transit from RUNNING to WAITING_FOR_EXECUTION
[component_container_mt-33] 
[component_container_mt-33] [WARN] [1759039207.825114675] [planning.scenario_planning.lane_driving.behavior_planning.behavior_path_planner.RTCInterface[start_planner]]: [updateCooperateStatus] uuid : 65e665ef19723cdd15b6fb20b5bb33de cannot transit from RUNNING to WAITING_FOR_EXECUTION

Expected behavior

none

Actual behavior

none

Steps to reproduce

none

Versions

No response

Possible causes

No response

Additional context

No response

[kosuke55]

@a-strong-python
sorry for the inconvinient, start planner can generate only the path inside lane, so you need to set ego vehicle inside lanes.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity.