feat: apply agnocast for planning&control #1659
Draft
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
Building on the previous PR, this change applies Agnocast to the nodes within the planning and control components.
This requires propagating the
use_agnocastandagnocast_heaphook_pathvalues down to the respective downstream launch files.For a detailed explanation of the parameters and the overall approach to integrating Agnocast into Autoware, please refer to the description of the initial PR.
How was this PR tested?
Verified the application by successfully running lsim (logging simulator) and psim (planning simulator) after applying the changes to the /perception/obstacle_segmentation/pointcloud topic.
Notes for reviewers
The documentation regarding the use of Agnocast in Autoware is available at the link below.
https://github.com/autowarefoundation/autoware_universe/blob/main/common/autoware_agnocast_wrapper/README.md
Furthermore, the following subsequent PRs will be updating other launch files not covered in this PR to also propagate use_agnocast and agnocast_heaphook_path.
Effects on system behavior
None.