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

Cleanup the README.rst for the lifecycle demo. #508

Merged
merged 2 commits into from
Apr 22, 2021

Conversation

clalancette
Copy link
Contributor

Signed-off-by: Chris Lalancette clalancette@openrobotics.org

This should fix #505

lifecycle/README.rst Show resolved Hide resolved
lifecycle/README.rst Show resolved Hide resolved
lifecycle/README.rst Show resolved Hide resolved
@clalancette
Copy link
Contributor Author

I made the changes you suggested in 2528366 . Please take another look.

lifecycle/README.rst Outdated Show resolved Hide resolved
In the following tutorial, we explain the purpose of these nodes, what makes them different from regular nodes and how they comply to a lifecycle management.
Managed nodes are scoped within a state machine of a finite amount of states.
These states can be changed by invoking a transition id which indicates the succeeding consecutive state.
The state machine is implemented as described at the `ROS2 design page <http://design.ros2.org/articles/node_lifecycle.html>`__.
The state machine is implemented as described at the `ROS 2 design page <http://design.ros2.org/articles/node_lifecycle.html>`__.

Our implementation differentiates between ``Primary States`` and ``Transition States``.
Primary States are supposed to be steady states in which any node can do the respected task.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this terminology is awkward. A state machine has states and transitions. I think it's potentially confusing to define a "transition state."

Copy link
Contributor Author

Choose a reason for hiding this comment

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

While I agree with you in an abstract sense, we do indeed define "transition states" as part of the state machine: https://github.com/ros2/rcl_interfaces/blob/master/lifecycle_msgs/msg/State.msg . So this sentence matches the code, even though the terminology is a bit weird.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok. Good that the docs are in sync.

lifecycle/README.rst Outdated Show resolved Hide resolved
lifecycle/README.rst Show resolved Hide resolved
lifecycle/README.rst Outdated Show resolved Hide resolved
Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
@clalancette clalancette force-pushed the clalancette/cleanup-lifecycle-readme branch from 2528366 to 3556153 Compare April 22, 2021 18:32
In the following tutorial, we explain the purpose of these nodes, what makes them different from regular nodes and how they comply to a lifecycle management.
Managed nodes are scoped within a state machine of a finite amount of states.
These states can be changed by invoking a transition id which indicates the succeeding consecutive state.
The state machine is implemented as described at the `ROS2 design page <http://design.ros2.org/articles/node_lifecycle.html>`__.
The state machine is implemented as described at the `ROS 2 design page <http://design.ros2.org/articles/node_lifecycle.html>`__.

Our implementation differentiates between ``Primary States`` and ``Transition States``.
Primary States are supposed to be steady states in which any node can do the respected task.
Copy link
Contributor

Choose a reason for hiding this comment

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

Ok. Good that the docs are in sync.

@clalancette
Copy link
Contributor Author

Merging without CI as this is only in the README file. Thanks for the reviews!

@clalancette clalancette merged commit 6f1390b into master Apr 22, 2021
@delete-merged-branch delete-merged-branch bot deleted the clalancette/cleanup-lifecycle-readme branch April 22, 2021 20:39
@clalancette
Copy link
Contributor Author

@Mergifyio backport galactic

mergify bot pushed a commit that referenced this pull request Apr 26, 2021
* Cleanup the README.rst for the lifecycle demo.

Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
(cherry picked from commit 6f1390b)
@mergify
Copy link

mergify bot commented Apr 26, 2021

Command backport galactic: success

Backports have been created

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.

The lifecycle demo README needs updating
3 participants