docs: reflect rename of sample descriptions

docs/demos/digital-twin-demos/carla-tutorial.md

@@ -29,7 +29,7 @@ TensorRT-optimized Vectorized Autonomous Driving ([VAD](https://github.com/hustv
      ```bash
      ros2 launch autoware_launch e2e_simulator.launch.xml \
        map_path:=$HOME/autoware_map/Town01 \
-       vehicle_model:=sample_vehicle \
+       vehicle_model:=autoware_sample_vehicle \
        sensor_model:=carla_sensor_kit \
        simulator_type:=carla \
        use_e2e_planning:=true \

docs/demos/planning-sim/index.md

@@ -39,7 +39,7 @@ If not, please, follow [Manual downloading of artifacts](https://github.com/auto
 
 ```bash
 source ~/autoware/install/setup.bash
-ros2 launch autoware_launch planning_simulator.launch.xml map_path:=$HOME/autoware_map/sample-map-planning vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit
+ros2 launch autoware_launch planning_simulator.launch.xml map_path:=$HOME/autoware_map/sample-map-planning vehicle_model:=autoware_sample_vehicle sensor_model:=autoware_sample_sensor_kit
 ```
 
 !!! warning

docs/demos/planning-sim/lane-change.md

@@ -11,7 +11,7 @@
 
    ```bash
    source ~/autoware/install/setup.bash
-   ros2 launch autoware_launch planning_simulator.launch.xml map_path:=$HOME/autoware_map/nishishinjuku_autoware_map vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit
+   ros2 launch autoware_launch planning_simulator.launch.xml map_path:=$HOME/autoware_map/nishishinjuku_autoware_map vehicle_model:=autoware_sample_vehicle sensor_model:=autoware_sample_sensor_kit
    ```
 
    ![open-nishishinjuku-map](images/lane-change/open-nishishinjuku-map.png)

docs/demos/planning-sim/lane-driving.md

@@ -4,7 +4,7 @@
 
 ```bash
 source ~/autoware/install/setup.bash
-ros2 launch autoware_launch planning_simulator.launch.xml map_path:=$HOME/autoware_map/sample-map-planning vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit
+ros2 launch autoware_launch planning_simulator.launch.xml map_path:=$HOME/autoware_map/sample-map-planning vehicle_model:=autoware_sample_vehicle sensor_model:=autoware_sample_sensor_kit
 ```
 
 !!! warning

docs/demos/rosbag-replay-simulation.md

@@ -53,7 +53,7 @@
 
    ```sh
    source ~/autoware/install/setup.bash
-   ros2 launch autoware_launch logging_simulator.launch.xml map_path:=$HOME/autoware_map/sample-map-rosbag vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit
+   ros2 launch autoware_launch logging_simulator.launch.xml map_path:=$HOME/autoware_map/sample-map-rosbag vehicle_model:=autoware_sample_vehicle sensor_model:=autoware_sample_sensor_kit
    ```
 
    Note that you cannot use `~` instead of `$HOME` here.

docs/demos/scenario-simulation/scenario-simulator/random-test-simulation.md

@@ -19,8 +19,8 @@
    ```bash
    ros2 launch random_test_runner random_test.launch.py \
      architecture_type:=awf/universe/20250130 \
-     sensor_model:=sample_sensor_kit \
-     vehicle_model:=sample_vehicle
+     sensor_model:=autoware_sample_sensor_kit \
+     vehicle_model:=autoware_sample_vehicle
    ```
 
 ![random_test_runner](images/random_test_runner.png)

docs/demos/scenario-simulation/scenario-simulator/scenario-test-simulation.md

@@ -21,8 +21,8 @@
      architecture_type:=awf/universe/20250130 \
      record:=false \
      scenario:='$(find-pkg-share scenario_test_runner)/scenario/sample.yaml' \
-     sensor_model:=sample_sensor_kit \
-     vehicle_model:=sample_vehicle \
+     sensor_model:=autoware_sample_sensor_kit \
+     vehicle_model:=autoware_sample_vehicle \
      use_custom_centerline:=true \
      rviz_config:=$(ros2 pkg prefix autoware_launch)/share/autoware_launch/rviz/scenario_simulator.rviz
    ```

docs/installation/autoware/docker-installation.md

@@ -59,7 +59,7 @@ For more launch options, you can append a custom launch command instead of using
 Here is an example of running the runtime container with a custom launch command:
 
 ```bash
-./docker/run.sh --map-path ~/autoware_map/sample-map-rosbag --data-path ~/autoware_data ros2 launch autoware_launch planning_simulator.launch.xml map_path:=/autoware_map vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit
+./docker/run.sh --map-path ~/autoware_map/sample-map-rosbag --data-path ~/autoware_data ros2 launch autoware_launch planning_simulator.launch.xml map_path:=/autoware_map vehicle_model:=autoware_sample_vehicle sensor_model:=autoware_sample_sensor_kit
 ```
 
 !!! info

docs/simulation-evaluation/components_evaluation/localization_evaluation/urban-environment-evaluation.md

@@ -2,7 +2,7 @@
 
 #### Related Links
 
 Data Collection Documentation --> [İstanbul Open Dataset](../../../datasets/index.md#istanbul-open-dataset)
 
 #### Purpose
 
@@ -22,7 +22,7 @@
 - 1 x Applanix POS LVX GNSS/INS System
 - 1 x Hesai Pandar XT32 LiDAR
 
 You can find the data collected for testing and mapping in this [İstanbul Open Dataset](../../../datasets/index.md#istanbul-open-dataset).
 
 > <span style="color:green">**NOTE !**</span> </br>  
 > Since there was no velocity source coming from the vehicle during all these tests, the twist message coming from GNSS/INS was given to ekf_localizer as the linear&angular velocity source. </br>
@@ -55,7 +55,7 @@
 ```
 
 > <span style="color:green">**NOTE !**</span></br>  
 > You also need to add `lanelet2_map.osm` file to autoware_ista_map folder. Since no lanelet file is created for this map at the
 > moment, you can run any `lanelet2_map.osm` file by placing it in this folder.
 
 2.) Download the test rosbag files.
@@ -107,7 +107,7 @@
 
 ```bash
 source ~/autoware/install/setup.bash
-ros2 launch autoware_launch logging_simulator.launch.xml map_path:=~/autoware_ista_map/ vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit
+ros2 launch autoware_launch logging_simulator.launch.xml map_path:=~/autoware_ista_map/ vehicle_model:=autoware_sample_vehicle sensor_model:=autoware_sample_sensor_kit
 ```
 
 ##### Run Rosbag
@@ -132,8 +132,8 @@
 gdown --id 1WPWmFCjV7eQee4kyBpmGNlX7awerCPxc -O ~/autoware_ista_map/
 ```
 
-> <span style="color:green">**NOTE !**</span></br>  
+> <span style="color:green">**NOTE !**</span></br>
 > You also need to add `lanelet2_map.osm` file to autoware_ista_map folder. Since no lanelet file is created for this map at the
 > moment, you can run any `lanelet2_map.osm` file by placing it in this folder.
 
 2.) Download the test rosbag files.
@@ -189,7 +189,7 @@
 
 From this point on, we move on to the bridge scenario. This is one of the bridges connecting the Bosphorus and was the longest bridge on our route. Here too, we thought that NDT-based localization might be disrupted. However, I did not observe any disruption.
 
 After this part there is another tunnel(Kagithane - Bomonti) and localization behaves similar to Eurasia tunnel. However, at the exit of this tunnel, it recovers localization on its own without the need for re-initialization.
 
 ##### Test 1 Summary
 

docs/tutorials/others/planning-evaluation-using-scenarios.md

@@ -162,8 +162,8 @@
 ros2 launch scenario_test_runner scenario_test_runner.launch.py \
 record:=false \
 scenario:='/path/to/scenario/sample.yaml' \
-sensor_model:=sample_sensor_kit \
-vehicle_model:=sample_vehicle \
+sensor_model:=autoware_sample_sensor_kit \
+vehicle_model:=autoware_sample_vehicle \
 use_custom_centerline:=true \
 rviz_config:=$(ros2 pkg prefix autoware_launch)/share/autoware_launch/rviz/scenario_simulator.rviz
 ```
@@ -192,7 +192,7 @@
 - Firstly, you should create a free TIER IV account to access the Autoware Evaluator. You can create an account by using
   the [TIER IV account creation page](https://account.tier4.jp/registration).
 
 - After you created an account, please reach out to Hiroshi IGATA (<hiroshi.igata@tier4.jp>), the AWF ODD WG leader, for
   an invitation to AWF project of the Autoware Evaluator. It is advised to join the ODD WG meeting once to briefly
   introduce yourself and your interest. The ODD WG information
   is [here](https://github.com/autowarefoundation/autoware-projects/wiki/operational-design-domain-working-group#how-to-participate-in-the-working-group).
@@ -262,7 +262,7 @@
 
 This page show us the detailed information of the failed case. We can understand why the case failing by looking into
 the `Message`. For our case, the message
 is `Simulation failure: CustomCommandAction typed "exitFailure" was triggered by the anonymous Condition (OpenSCENARIO.Storyboard.Story[0].Act["_EndCondition"].ManeuverGroup[0].Maneuver[0].Event[1].StartTrigger.ConditionGroup[1].Condition[0]): The state of StoryboardElement "act_ego_nostop_check" (= completeState) is given state completeState?`
 
 From this message, we can understand that an action which is used for checking the vehicle is not stopped is in complete
 state. And, the scenario author set this condition as a failure condition. Therefore, the scenario failed.

docs/tutorials/others/using-divided-map.md

@@ -18,7 +18,7 @@ Note that you need to specify the `map_path` and `pointcloud_map_file` arguments
 source ~/autoware/install/setup.bash
 ros2 launch autoware_launch logging_simulator.launch.xml \
   map_path:=$HOME/autoware_map/sample-map-rosbag pointcloud_map_file:=pointcloud_map \
-  vehicle_model:=sample_vehicle_split sensor_model:=sample_sensor_kit
+  vehicle_model:=autoware_sample_vehicle_split sensor_model:=autoware_sample_sensor_kit
 ```
 
 For playing rosbag to simulate Autoware, please refer to the instruction in [the demo for rosbag replay simulation](../../demos/rosbag-replay-simulation.md).