-
Notifications
You must be signed in to change notification settings - Fork 145
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: add 'parameters.md' in ros-nodes #220
Conversation
ff08b4a
to
8e94b6c
Compare
Nice PR! FYI: I explained how we manage parameters in Autoware in this PR. Regarding the content, it seems almost no conflict among our PRs. 👍 |
Parameters in ROS are associated with individual nodes. Parameters are used to configure nodes at startup (and during runtime), without changing the code. The lifetime of a parameter is tied to the lifetime of the node (though the node could implement some sort of persistence to reload values after restart).<br> | ||
Parameters are addressed by node name, node namespace, parameter name, and parameter namespace. Providing a parameter namespace is optional.<br> | ||
Each parameter consists of a key, a value, and a descriptor. The key is a string and the value is one of the following types: bool, int64, float64, string, byte[], bool[], int64[], float64[] or string[]. By default all descriptors are empty, but can contain parameter descriptions, value ranges, type information, and additional constraints.<br> | ||
For an hands-on tutorial with ROS parameters [see here](https://docs.ros.org/en/humble/Tutorials/Beginner-CLI-Tools/Understanding-ROS2-Parameters/Understanding-ROS2-Parameters.html) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since it's just a copy of https://docs.ros.org/en/humble/Concepts/About-ROS-2-Parameters.html#overview, we can simplify this part by linking it.
- get     Get parameter | ||
- list      Output a list of available parameters | ||
- load       Load parameter file for a node | ||
- set      Set parameter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part can also be replaced by https://docs.ros.org/en/foxy/How-To-Guides/Using-ros2-param.html.
1000ms, std::bind(&MinimalParam::timer_callback, this)); | ||
} | ||
} | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shulanbushangshu Thank you for writing this. |
Signed-off-by: jack.song <jack.song@autocore.ai>
a76b70f
to
6d4caf9
Compare
Signed-off-by: jack.song <jack.song@autocore.ai>
e3bf5df
to
6b18b59
Compare
Signed-off-by: jack.song <jack.song@autocore.ai>
110b843
to
6cd1545
Compare
Signed-off-by: jack.song <jack.song@autocore.ai>
e51dfa0
to
c0a1544
Compare
Signed-off-by: jack.song <jack.song@autocore.ai>
58c0ad9
to
dc24538
Compare
Signed-off-by: jack.song <jack.song@autocore.ai>
eb57358
to
361cefa
Compare
Related: #271 (comment) |
This pull request has been automatically marked as stale because it has not had recent activity. |
@shulanbushangshu What is the current status of this PR? |
@mitsudome-r |
@shulanbushangshu Could you update the branch with latest main branch? It makes it easier for me to see the diffs with current documentation. Also, you might want to integrate some of the guidelines regarding parameters discussed in this thread.
|
@mitsudome-r |
Signed-off-by: jack.song jack.song@autocore.ai
Description
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.
In-review checklist for the PR reviewers
The Reviewers must check the checkboxes below before approval.
Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.
After all checkboxes are checked, anyone who has write access can merge the PR.