-
Notifications
You must be signed in to change notification settings - Fork 431
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
Parameters not set from the command-line using new syntax #860
Comments
@hidmic FYI |
Alright, it looks like in between changes to |
🙇♂️ |
@hidmic Looks like this was fixed? Though I don't know by what changes exactly. |
Yes it was! By ros2/rcl#508 and #865. Closing. |
I see this issue in rclpy. the question seems to be related |
@hamaney If you installed ROS 2 with As pointed out on ROS answers, this method for passing ROS parameters is only supported since ROS 2 Eloquent. So if you are using ROS 2 Dashing, it will not work. If you continue to have problems, please comment on ROS Answers (or create a new question) with details about your installation. This lets other users benefit from the answer. (GitHub tickets are not as visible) |
Sorry, my mistake. I know the distro of ROS2 that I am using, which is Dashing as you mentioned. |
@hamaney No worries. Because ROS follows a federated model for packages, each package has a version number, but ROS distro as a whole just has a name (e.g. Dashing). If you want to know the particular version of a package, you can use the following # Get the version of rclcpp
ros2 pkg xml rclcpp --tag version |
ros2#860) * Allow forward slashes within a parameter name rule in argument parsing Signed-off-by: Ivan Santiago Paunovic <ivanpauno@ekumenlabs.com>
Bug report
Required Info:
Steps to reproduce issue
Create a simple node that echos a parameter:
Run the node and try to set the parameter "foo":
Expected behavior
The node prints the value set from the command line:
Actual behavior
The node prints the default value:
Additional information
Passing the parameter via a YAML file works fine, e.g
params.yaml
and running
The text was updated successfully, but these errors were encountered: