Move out ekf_localizer
params from the xml launch file to a dedicated yaml config file
#2958
Closed
3 tasks done
Labels
type:new-feature
New functionalities or additions, feature requests.
Checklist
Description
Currently,
ekf_localizer
params are all hardcoded in theekf_localizer.launch.xml
file. This is inconsistent with other packages, for which launch files and runtime parameters are split in different files.For example for
ndt_scan_matcher.param.yaml
:src/autoware.universe/localization/ndt_scan_matcher/launch/ndt_scan_matcher.launch.xml
src/autoware.universe/localization/ndt_scan_matcher/config/ndt_scan_matcher.param.yaml
autoware_launch
config insrc/launcher/autoware_launch/autoware_launch/config/localization/ndt_scan_matcher.param.yaml
https://github.com/autowarefoundation/autoware_launch/blob/main/autoware_launch/config/localization/ndt_scan_matcher.param.yaml
Purpose
Make
ekf_localizer
consistent with other packages.Separating params from the launch file makes it easier to override the configuration.
Possible approaches
To keep the current behavior, we could have:
src/universe/autoware.universe/localization/ekf_localizer/config/ekf_localizer.param.yaml
:src/launcher/autoware_launch/autoware_launch/config/localization/ekf_localizer.param.yaml
:src/universe/autoware.universe/localization/ekf_localizer/launch/ekf_localizer.launch.xml
:src/launcher/autoware_launch/autoware_launch/launch/components/tier4_localization_component.launch.xml
, add:src/universe/autoware.universe/launch/tier4_localization_launch/launch/localization.launch.xml
, add:src/universe/autoware.universe/launch/tier4_localization_launch/launch/pose_twist_fusion_filter/pose_twist_fusion_filter.launch.xml
, add:Definition of done
ekf_localizer
runtime parameters are loaded from dedicated config files instead of being hardcoded in its launch file.The text was updated successfully, but these errors were encountered: