chore(autoware_launch): add localization_input_pointcloud argument to autoware.launch #712
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I have modified Autoware to allow specifying the topic name for the point cloud used in localization module as an command-line argument.
(A solution for addressing scenarios involving the external modification of point clouds used in localization, followed by the execution of identical scenario evaluations to compare results. TIER IV INTERNAL LINK )
Tests performed
I have checked that planning_simulator launches successfully.
$ros2 launch autoware_launch planning_simulator.launch.xml vehicle_id:=default vehicle_model:=lexus sensor_model:=aip_xx1 map_path:=[MAP_PATH]
I have checked that the parameters of localization_input_pointcloud are successfully reflected in the localization module."
$ros2 launch autoware_launch autoware.launch.xml vehicle_id:=default vehicle_model:=lexus sensor_model:=aip_xx1 map_path:=[MAP_PATH] localization_input_pointcloud:=/x
$ros2 node info /localization/util/crop_box_filter_measurement_range
Effects on system behavior
Not applicable ( There is no effect on the default behavior ).
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.
In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.
Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.
After all checkboxes are checked, anyone who has write access can merge the PR.