Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(tier4_localization_component_launch): add an option not to use exisitng pointcloud preprocessing node containers #890

Conversation

TaikiYamada4
Copy link
Contributor

@TaikiYamada4 TaikiYamada4 commented Feb 27, 2024

Description

We had a discussion to change the default input_pointcloud to be /sensing/lidar/concatenated/pointcloud, and we need an option to launch a node container only for pointcloud preprocessing nodes in the localization component (/localization/util/....) since we cannot load these to the fully loaded /pointcloud_container.

See the PR in autoware.universe for more information.

The argument lidar_container_name is changed to target_pointcloud_container_name since it might not be a node container related to a specific LiDAR.

Related links

This PR has to be merged with this PR in autoware.universe!!

Tests performed

I tested this launch system via the logging_simulator tutorial and get the following results when I ros2 component list

(Excerpted)
/localization/util/pointcloud_preprocessor/pointcloud_container
  1  /localization/util/crop_box_filter_measurement_range
  2  /localization/util/voxel_grid_downsample_filter
  3  /localization/util/random_downsample_filter

Notes for reviewers

This PR has to be merged with this PR in autoware.universe!!

Interface changes

A new node_container named /localization/util/pointcloud_preprocessor/pointcloud_container will be launched, and /localization/util/crop_box_filter_measurement_range, /localization/util/voxel_grid_downsample_filter, and /localization/util/random_downsample_filter will be added to it.

Effects on system behavior

If the user didn't define target_pointcloud_container_name by commenting it out, the pointcloud publication/subscription between sensing & localization components will be done outside the node container, which leads to an increase of latency. (about + 20ms in my PC).

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.

  • The PR follows the pull request guidelines.
  • The PR has been properly tested.
  • The PR has been reviewed by the code owners.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

  • There are no open discussions or they are tracked via tickets.
  • The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

… be able to choose whether to launch a new node_container for the localization.

Signed-off-by: TaikiYamada4 <[email protected]>
yuki-takagi-66 pushed a commit to tier4/autoware_launch that referenced this pull request Jul 3, 2024
…oundation#890)

* fix_pointpainting_path

Signed-off-by: Yuxuan Liu <[email protected]>

* style(pre-commit): autofix

* merge

Signed-off-by: Yuxuan Liu <[email protected]>

* add centerpoint_xx1 param

Signed-off-by: Yuxuan Liu <[email protected]>

* style(pre-commit): autofix

---------

Signed-off-by: Yuxuan Liu <[email protected]>
Co-authored-by: Yuxuan Liu <[email protected]>
Co-authored-by: Owen-Liuyuxuan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant