refactor(autoware_velocity_smoother): rework parameters

[batuhanbeytekin]

Description

Implement the ROS Node configuration layout described in https://github.com/orgs/autowarefoundation/discussions/3371

Tests performed

Package built and launch locally.

Effects on system behavior

More reliable and faster parameter configuration file creation.

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

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.

[github-actions]

Thank you for contributing to the Autoware project!

🚧 If your pull request is in progress, switch it to draft mode.

Please ensure:

• You've checked our contribution guidelines.
• Your PR follows our pull request guidelines.
• All required CI checks pass before marking the PR ready for review.

[github-actions]

Documentation URL: https://autowarefoundation.github.io/autoware.universe/pr-8298/
Modified URLs:

• https://autowarefoundation.github.io/autoware.universe/pr-8298/planning/autoware_velocity_smoother/ja/
• https://autowarefoundation.github.io/autoware.universe/pr-8298/planning/autoware_velocity_smoother/

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 26.14%. Comparing base (01d9d67) to head (a060a63).
Report is 1010 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8298      +/-   ##
==========================================
- Coverage   26.16%   26.14%   -0.02%     
==========================================
  Files        1302     1306       +4     
  Lines       96917    96964      +47     
  Branches    39150    39152       +2     
==========================================
  Hits        25354    25354              
- Misses      68900    68947      +47     
  Partials     2663     2663              

Flag	Coverage Δ		*Carryforward flag
differential	23.02% <ø> (?)
total	26.16% <ø> (ø)		Carriedforward from 01d9d67

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[batuhanbeytekin]

Hi @TakaHoribe, @go-sakayori, @mkuri, @rej55, @satoshi-ota,
One approval is needed to merge this PR. Could you please review it?

[mitsudome-r]

Is it possible to split these two parameters as default_nearest_search.param.yaml under config folder?

[mitsudome-r]

These parameters are meant to be managed as common parameter among different nodes and is better to be managed as a separate file.

[batuhanbeytekin]

Is it possible to split these two parameters as default_nearest_search.param.yaml under config folder?

I will make the necessary updates as you said. Thanks for your feedback.

[mitsudome-r]

Could you change this to the following code so that the argument passed to the launch file is used instead?

Suggested change

	algorithm_type: "JerkFiltered" # algorithm type for velocity smoother. "JerkFiltered" or "L2" or "Linf" or "Analytical"
	algorithm_type: $(var velocity_smoother_type) # algorithm type for velocity smoother. "JerkFiltered" or "L2" or "Linf" or "Analytical"

[stale]

This pull request has been automatically marked as stale because it has not had recent activity.

[mitsudome-r]

@oguzkaganozt We should have someone to take over this PR.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity.