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(imu_launch): add gyro_bias_estimator.param.yaml #232

Merged
merged 4 commits into from
Apr 22, 2024

Conversation

TaikiYamada4
Copy link
Contributor

Description

Till today, the parameters of gyro_bias_estimator was called from universe/sensing/imu_corrector/config/gyro_bias_estimator.param.yaml, which is not reachable from the launching system.

However, some values in the gyro_bias_estimator.param.yaml should be changed by product requirements.

Therefore, this PR allows the system to edit the gyro_bias_estimator.param.yaml without touching the autoware.universe.

Testing

The system was tested via the logging simulator of xx1 system.
I checked it by ros2 param dump that the parameters are loaded from common_sensor_launch/config/ and local changes were applied if they exist.

Related PRs

This PR is an alternative of #220, so #220 should be deleted when this PR is merged.

@TaikiYamada4 TaikiYamada4 requested a review from shmpwk April 16, 2024 06:32
@TaikiYamada4 TaikiYamada4 self-assigned this Apr 16, 2024
@TaikiYamada4 TaikiYamada4 changed the title feat(imu_launch): add gyro_bias_estimator.param.yaml feat(imu_launch): add gyro_bias_estimator.param.yaml Apr 16, 2024
Copy link
Contributor

@shmpwk shmpwk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@shmpwk shmpwk merged commit 101480d into tier4/universe Apr 22, 2024
9 of 10 checks passed
@shmpwk shmpwk deleted the feat/add_gyro_bias_params branch April 22, 2024 06:33
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.

2 participants