-
Notifications
You must be signed in to change notification settings - Fork 224
replaced <ros2-distro> with $ROS_DISTRO #658
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
Open
glitchhopcore
wants to merge
1
commit into
ros-navigation:master
Choose a base branch
from
glitchhopcore:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,16 +18,16 @@ Requirements | |
|
||
1- Install Camera Calibration Parser, Camera Info Manager and Launch Testing Ament Cmake using operating system’s package manager: | ||
|
||
``sudo apt install ros-<ros2-distro>-camera-calibration-parsers`` | ||
``sudo apt install ros-$ROS_DISTRO-camera-calibration-parsers`` | ||
|
||
``sudo apt install ros-<ros2-distro>-camera-info-manager`` | ||
``sudo apt install ros-$ROS_DISTRO-camera-info-manager`` | ||
|
||
``sudo apt install ros-<ros2-distro>-launch-testing-ament-cmake`` | ||
``sudo apt install ros-$ROS_DISTRO-launch-testing-ament-cmake`` | ||
|
||
|
||
2- Image Pipeline need to be built from source in your workspace with: | ||
|
||
``git clone -b <ros2-distro> [email protected]:ros-perception/image_pipeline.git`` | ||
``git clone -b $ROS_DISTRO [email protected]:ros-perception/image_pipeline.git`` | ||
|
||
|
||
**Also, make sure you have the following:** | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,11 +27,11 @@ If you don't have them installed, please follow :ref:`getting_started`. | |
|
||
SLAM Toolbox can be installed via: | ||
|
||
``sudo apt install ros-<ros2-distro>-slam-toolbox`` | ||
``sudo apt install ros-$ROS_DISTRO-slam-toolbox`` | ||
|
||
or from built from source in your workspace with: | ||
|
||
``git clone -b <ros2-distro>-devel [email protected]:stevemacenski/slam_toolbox.git`` | ||
``git clone -b $ROS_DISTRO-devel [email protected]:stevemacenski/slam_toolbox.git`` | ||
|
||
|
||
Tutorial Steps | ||
|
@@ -45,14 +45,14 @@ The turtlebot3 software can be installed via the following or on the `turtlebot3 | |
|
||
.. code-block:: bash | ||
sudo apt install ros-<ros2-distro>-turtlebot3 ros-<ros2-distro>-turtlebot3-msgs ros-<ros2-distro>-turtlebot3-bringup | ||
sudo apt install ros-$ROS_DISTRO-turtlebot3 ros-$ROS_DISTRO-turtlebot3-msgs ros-$ROS_DISTRO-turtlebot3-bringup | ||
If you have another robot, replace with your robot specific interfaces. | ||
Typically, this includes the robot state publisher of the URDF, simulated or physical robot interfaces, controllers, safety nodes, and the like. | ||
|
||
Run the following commands first whenever you open a new terminal during this tutorial. | ||
|
||
- ``source /opt/ros/<ros2-distro>/setup.bash`` | ||
- ``source /opt/ros/$ROS_DISTRO/setup.bash`` | ||
- ``export TURTLEBOT3_MODEL=waffle`` | ||
|
||
|
||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -59,11 +59,11 @@ Follow the same process as in :ref:`getting_started` for installing and setting | |
|
||
STVL can be installed in ROS 2 via the ROS Build Farm: | ||
|
||
- ``sudo apt install ros-<ros2-distro>-spatio-temporal-voxel-layer`` | ||
- ``sudo apt install ros-$ROS_DISTRO-spatio-temporal-voxel-layer`` | ||
|
||
It can also be built from source by cloning the repository into your Navigation2 workspace: | ||
|
||
- ``git clone -b <ros2-distro>-devel [email protected]:stevemacenski/spatio_temporal_voxel_layer`` | ||
- ``git clone -b $ROS_DISTRO-devel [email protected]:stevemacenski/spatio_temporal_voxel_layer`` | ||
|
||
1- Modify Navigation2 Parameter | ||
------------------------------- | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
A note: the
ROS_DISTRO
env variable isn't set before you source the setup.bash file, so that would not be in your environment yet to work. This is actually true of several of the changes in this PR.Do you think that may cause more problems than it solves if when using
ROS_DISTRO
when not set it will return an empty string? I feel like that might confuse users if they get errors trying to accesssource /opt/ros//setup.bash
orapt install ros--gazebo-ros-pkgs
because the variable is not setUh oh!
There was an error while loading. Please reload this page.
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 guess you are right, it would definitely make it more confusing.
Furthermore for places like
build_docs/index.rst
, we seem tosource /opt/ros/<distro>/setup.bash
, do you think we should suggest users to havesetup.bash
sourced before running the commands wherever I have mentioned the changes, or do you think there is a better way to handle this, or if it is alright as it is?Uh oh!
There was an error while loading. Please reload this page.
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.
That would help for this case, but I think for all cases where you need to source (at least), then we would need to not use
ROS_DISTRO
. I think that counts for more than just in the build docs -- it might be worth looking over your changes and see for what other situations we haven't yet told the user to source the setup script and add that too (or leave as-is)