Skip to content

Conversation

@domire8
Copy link
Member

@domire8 domire8 commented May 31, 2024

Description

This PR solves the parent issue by adding a pre_set_parameters_callback to the component interfaces. Because the parametres in that feedback are mutable, we can basically run the whole validation in this callback, and just forward the result to the on_set_parameters_callback.

It required some other changes that are rather hard to describe because of the somewhat complex call sequence in ROS but I'm happy to discuss any open points.

If you like it, I have to do the same in the modulo controllers.

Review guidelines

Estimated Time of Review: 15 minutes

Checklist before merging:

  • Confirm that the relevant changelog(s) are up-to-date in case of any user-facing changes

@domire8 domire8 force-pushed the fix/parameter-set-vali branch from 40502a3 to e18b938 Compare June 10, 2024 06:16
Copy link
Member

@eeberhard eeberhard left a comment

Choose a reason for hiding this comment

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

Looking very promising in general!

Copy link
Member

@eeberhard eeberhard left a comment

Choose a reason for hiding this comment

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

Cool!

@domire8 domire8 changed the title fix: keep parameter values in sync with ros fix(components): keep parameter values in sync with ros Jun 11, 2024
@domire8 domire8 merged commit 32c1d6c into breaking Jun 11, 2024
@domire8 domire8 deleted the fix/parameter-set-vali branch June 11, 2024 05:25
@github-actions github-actions bot locked and limited conversation to collaborators Jun 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Setting a parameter can create a mismatch in parameter value between the internal value and the ros2 param value

2 participants