-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Intermediate launch tutorial #2002
Conversation
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.
Looks pretty good.
Some high level feedback:
- Think about where you will end paragraphs. In general, I think of one paragraph as one idea. It should be fairly self-contained. I've advised combining several paragraphs.
- Make sure to be clear about parameters and arguments. In some sections it seems that they are used interchangeably, but they are different.
- Lastly, this PR seemed to have more grammar mistakes and typos than some of your previous PRs. Make sure to give it a proofread before marking the PR as ready for review.
That being said, overall the content is really good. Thanks for putting this together!
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
I have now included some more content covering basics of using namespaces and wildcards. However, this tutorial does not go into a lot of details and tries to cover as much content as possible. More in depth tutorials could definitively be helpful, especially the one covering more wildcard syntax like |
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.
just a small comment
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
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.
Looks better. I've added a few phrasing changes.
Do you think it would be good to also cover the wildcard within a namespace? (See comment)
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
source/Tutorials/Launch-Files/Using-ROS2-Launch-For-Large-Projects.rst
Outdated
Show resolved
Hide resolved
|
||
.. code-block:: YAML | ||
|
||
/**: |
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.
It would also be good to show how to use the wildcard operator to set parameters for a subset of nodes (which I think is possible). For example, something like, /turtles/**
, which would apply to nodes in the /turtles
namespace.
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.
I have omitted that for a time being as it currently does not work as expected. I tried to use that /**/sim
phrase, but it is not working. I mentioned my case here: ros2/design#303 (comment)
I believe also that design features are not yet fully defined as some related PRs and issues are still open ros2/rclcpp#1265 (comment).
Otherwise, do you know the way to make it work?
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 syntax could be added or covered in its own tutorial later as mentioned in #2002 (comment).
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.
Looks good to me, nice work!
@mergify backport foxy galactic |
* launch code and initial tutorial structure * add more information about ROS parameters * add sections on remappings and rviz config * update section on env variables * update code descriptions * add results section * remove pipfile * add setup.py configuration instructions * add prerequisites section * restructure and enumerate sections * apply review suggestions * fix grammar * add section on using namespaces * add subsection on wildcards * instruct to create a new launch file instead of updating the existing * minor fix * add reference to Creating your first ROS 2 package tutorial * apply suggestions (cherry picked from commit 9a63591)
* launch code and initial tutorial structure * add more information about ROS parameters * add sections on remappings and rviz config * update section on env variables * update code descriptions * add results section * remove pipfile * add setup.py configuration instructions * add prerequisites section * restructure and enumerate sections * apply review suggestions * fix grammar * add section on using namespaces * add subsection on wildcards * instruct to create a new launch file instead of updating the existing * minor fix * add reference to Creating your first ROS 2 package tutorial * apply suggestions (cherry picked from commit 9a63591)
Command
Hey, I reacted but my real name is @Mergifyio |
* launch code and initial tutorial structure * add more information about ROS parameters * add sections on remappings and rviz config * update section on env variables * update code descriptions * add results section * remove pipfile * add setup.py configuration instructions * add prerequisites section * restructure and enumerate sections * apply review suggestions * fix grammar * add section on using namespaces * add subsection on wildcards * instruct to create a new launch file instead of updating the existing * minor fix * add reference to Creating your first ROS 2 package tutorial * apply suggestions (cherry picked from commit 9a63591) Co-authored-by: kurshakuz <abilkasov@gmail.com>
* launch code and initial tutorial structure * add more information about ROS parameters * add sections on remappings and rviz config * update section on env variables * update code descriptions * add results section * remove pipfile * add setup.py configuration instructions * add prerequisites section * restructure and enumerate sections * apply review suggestions * fix grammar * add section on using namespaces * add subsection on wildcards * instruct to create a new launch file instead of updating the existing * minor fix * add reference to Creating your first ROS 2 package tutorial * apply suggestions (cherry picked from commit 9a63591) Co-authored-by: kurshakuz <abilkasov@gmail.com>
This tutorial shows the way to use launch files for large projects. It also shows examples of using parameters, YAML files, remappings, namespaces, default arguments, and RViz configs in launch files.
Signed-off-by: Shyngyskhan Abilkassov abilkasov@gmail.com