style(pre-commit): autofix

Author: pre-commit-ci[bot]

planning/autoware_static_centerline_generator/README.md

@@ -110,11 +110,11 @@ By default, footprint colors are:
 
 When embedding a fixed route from VMB, some routes may fail or produce incomplete centerlines. Common causes and remedies:
 
-| Symptom / Error | Cause | What to check |
-|-----------------|--------|----------------|
-| **LaneletsNotConnected** | The lane IDs in the route are not topologically connected (next lanelet of one is not the following in the list). | In VMB, ensure the selected lane sequence is connected in the map (no skipped lanes, correct direction). |
-| **PathNotFound** | Optimization returned no trajectory (e.g. goal_method, very sharp curve, or degenerate lane). | Check `goal_method` and route shape; try a shorter or simpler segment. |
-| **InvalidRoute** | Request had an empty route. | Ensure the route selection in VMB sends at least one lane ID. |
-| **InvalidLanelet** | Start/goal lanelet has no valid centerline (e.g. centerline has fewer than 2 points). | Fix or regenerate the map so that lanelets have valid centerlines. |
-| **Some lanelets with no points** | Optimized path does not pass through every selected lanelet, or points fall outside polygon (e.g. sharp curves). | Check terminal for `PlanPath: lanelet id X has no assigned points`. Adjust route or map; sharp curves may need manual centerline. |
-| **Points outside all lanelets** | Smoothed trajectory lies slightly outside lane polygons (boundaries or optimization). | Terminal logs: `X trajectory point(s) were outside all lanelet polygons`. Points are still assigned to the nearest segment; if embedding looks wrong, simplify the route or check map geometry. |
+| Symptom / Error                  | Cause                                                                                                             | What to check                                                                                                                                                                                   |
+| -------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **LaneletsNotConnected**         | The lane IDs in the route are not topologically connected (next lanelet of one is not the following in the list). | In VMB, ensure the selected lane sequence is connected in the map (no skipped lanes, correct direction).                                                                                        |
+| **PathNotFound**                 | Optimization returned no trajectory (e.g. goal_method, very sharp curve, or degenerate lane).                     | Check `goal_method` and route shape; try a shorter or simpler segment.                                                                                                                          |
+| **InvalidRoute**                 | Request had an empty route.                                                                                       | Ensure the route selection in VMB sends at least one lane ID.                                                                                                                                   |
+| **InvalidLanelet**               | Start/goal lanelet has no valid centerline (e.g. centerline has fewer than 2 points).                             | Fix or regenerate the map so that lanelets have valid centerlines.                                                                                                                              |
+| **Some lanelets with no points** | Optimized path does not pass through every selected lanelet, or points fall outside polygon (e.g. sharp curves).  | Check terminal for `PlanPath: lanelet id X has no assigned points`. Adjust route or map; sharp curves may need manual centerline.                                                               |
+| **Points outside all lanelets**  | Smoothed trajectory lies slightly outside lane polygons (boundaries or optimization).                             | Terminal logs: `X trajectory point(s) were outside all lanelet polygons`. Points are still assigned to the nearest segment; if embedding looks wrong, simplify the route or check map geometry. |

planning/autoware_static_centerline_generator/src/static_centerline_generator_node.cpp

@@ -158,8 +158,8 @@ std::vector<lanelet::Id> check_lanelet_connection(
 
 void assign_centerline_points_to_lanelets(
   const std::vector<TrajectoryPoint> & optimized_traj_points,
-  const lanelet::ConstLanelets & route_lanelets,
-  PlanPath::Response::SharedPtr response, const rclcpp::Logger & logger)
+  const lanelet::ConstLanelets & route_lanelets, PlanPath::Response::SharedPtr response,
+  const rclcpp::Logger & logger)
 {
   std::vector<std::vector<geometry_msgs::msg::Point>> points_per_lanelet(route_lanelets.size());
   size_t current_lanelet_idx = 0;
@@ -168,8 +168,9 @@ void assign_centerline_points_to_lanelets(
   for (const auto & traj_point : optimized_traj_points) {
     const auto pt = convert_to_lanelet_point(traj_point.pose.position);
 
-    if (current_lanelet_idx < route_lanelets.size() &&
-        lanelet::geometry::inside(route_lanelets.at(current_lanelet_idx), pt)) {
+    if (
+      current_lanelet_idx < route_lanelets.size() &&
+      lanelet::geometry::inside(route_lanelets.at(current_lanelet_idx), pt)) {
       points_per_lanelet.at(current_lanelet_idx).push_back(traj_point.pose.position);
       continue;
     }