tier4_simulator_launch

Structure

Package Dependencies

Please see <exec_depend> in package.xml.

Usage

  <include file="$(find-pkg-share tier4_simulator_launch)/launch/simulator.launch.xml">
    <arg name="vehicle_info_param_file" value="VEHICLE_INFO_PARAM_FILE" />
    <arg name="vehicle_model" value="VEHICLE_MODEL"/>
  </include>

The simulator model used in simple_planning_simulator is loaded from “config/simulator_model.param.yaml” in the “VEHICLE_MODEL_description” package.

Changelog for package tier4_simulator_launch

0.53.0 (2026-10-13)

• Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base

• refactor(localization)!: migrate tier4_localization_launch to autoware_localization_launch with a separate config package (#1971)

  * refactor(localization)!: migrate tier4_localization_launch to autoware_localization_launch with a separate config package Move the localization launch stack out of the product layer and split its parameter tree into autoware_localization_config. localization.launch.xml resolves every parameter file through localization_config_pkg; the launch graph is unchanged.

  * refactor(localization): move the localization design modules alongside the localization launch package The localization modules move into autoware_localization_launch/design/module, matching the planning and control layout; the parameter set and the wrapper resolve parameter files from autoware_localization_config.

  * refactor(localization): flatten pose/twist source selection into per-estimator junctions pose_source/twist_source string parsing moves into the product component; localization.launch.xml and pose_twist_estimator.launch.xml take one flag per estimator plus the arbiter's pose_sources list, so a fixed system can pin the junctions directly. The launch graph is unchanged.

  * refactor(localization): restore the module-shaped launch composition localization.launch.xml composes the same instances as Localization.module: the util module (pose initializer and the ndt input downsampling) becomes a sibling group with launch/util/util.launch.xml as the LocalizationUtil counterpart, and cross-module wiring (the arbiter relay input, eagleye standing in for the gnss pose) is resolved at the composition root. The launch graph is unchanged.

  * refactor(localization)!: compose localization from self-contained unit launchers The all-mode entry launchers (localization.launch.xml and pose_twist_estimator.launch.xml) are removed: the launch package ships one launcher per unit, each resolving only its own parameters from localization_config_pkg, and component_localization.launch.xml is the composition root that includes only the units the selected sources need — the perception layout. The unreferenced Tier4LocalizationWrapper design is dropped with its launch entry. The launch graph is unchanged.

  • style(pre-commit): autofix

  * fix(localization): connect the automatic pose initializer in LocalizationUtil Wires the pose initializer state and initialize service to automatic_pose_initializer, whose node design now declares the fixed API names as remap targets.

  * chore(localization): drop the exec_depends the composition root owns autoware_pose_estimator_arbiter and autoware_pose_covariance_modifier are included from component_localization.launch.xml, which autoware_launch declares.

  * docs(launch): drop the stale launch diagrams and retarget the config usage example Both package structure diagrams draw the localization.launch.xml composition this series removes, and the autoware_launch one also draws the simulator wrappers as if the root launcher called the sub launchers. The config package documents the composition root as the place localization_config_pkg is set.

  * fix(localization): resolve stop_check_enabled for every system run mode The stop check belongs to a real vehicle, so any run mode other than online disables it; the value is defined unconditionally so a product run mode outside the in-tree set still resolves.

  * chore(localization): carry the changelog over unedited The recorded entries reference upstream pull requests by their original package name, matching the control, planning and perception migrations. ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

• refactor(perception)!: extract the perception parameter tree into autoware_perception_config and modularize the simulated perception pipeline (#1955)

  • Refactor perception launch files to use autoware_perception_config package
  • Removed the perception_config_pkg argument from multiple launch files.
  • Updated parameter paths in various launch files to reference autoware_perception_config instead of perception_config_pkg.
  • Ensured consistency across object recognition, obstacle segmentation, occupancy grid map, and traffic light recognition launch files.
  • Added autoware_perception_config as a dependency in package.xml.
  • Refactor perception launch files to use dynamic configuration paths
  • Added a new argument [perception_config_pkg]{.title-ref} to specify the perception configuration package.
  • Introduced [perception_config_dir]{.title-ref} variable to

File truncated at 100 lines see the full file