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

parameter allows array values but only scalar limits #137

Open
christianrauch opened this issue Mar 23, 2022 · 0 comments
Open

parameter allows array values but only scalar limits #137

christianrauch opened this issue Mar 23, 2022 · 0 comments
Labels
backlog bug Something isn't working

Comments

@christianrauch
Copy link

Bug report

There is a discrepancy in the API design of the parameter values in ParameterValue and their bounds in (ParameterDescriptor).

While the parameter value allows scalar and array types:
https://github.com/ros2/rcl_interfaces/blob/1.2.0/rcl_interfaces/msg/ParameterValue.msg#L12-L38
the bounds in FloatingPointRange and IntegerRange are arrays with a single entry:
https://github.com/ros2/rcl_interfaces/blob/1.2.0/rcl_interfaces/msg/ParameterDescriptor.msg#L32-L36

What is the meaning of the scalar/single-element-array parameter ranges for array values? Having the bounds defined as arrays suggests that they are supposed to be used element-wise, which is not possible with the current message definition.

Expected behavior

Parameter limits in FloatingPointRange and IntegerRange should have the same dimension than the parameter value, such that every element in the value has its own min/max range.

Actual behavior

Parameter limits are scalar / single-element-array.

@clalancette clalancette added bug Something isn't working backlog labels Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants