Fix Garden documentation to remove ign for gz. (gazebosim#333)

Co-authored-by: Alejandro Hernández Cordero <[email protected]>
Co-authored-by: Mabel Zhang <[email protected]>

Author: 3 people

garden/comparison.md

@@ -245,7 +245,7 @@ Feature | Gazebo-classic | Gazebo Sim
 -- | -- | --
 ODE engine | ✓ | [Issue](https://github.com/gazebosim/gz-physics/issues/63)
 Bullet engine | ✓ | ✓
-DART engine | ✓ | ✓ Plugin shipped with ign-physics
+DART engine | ✓ | ✓ Plugin shipped with gz-physics
 Simbody engine | ✓ | [Issue](https://github.com/gazebosim/gz-physics/issues/63)
 TPE engine | ✕ | ✓
 Custom engine plugins | ✕ | ✓
@@ -278,7 +278,7 @@ Render order | ✕  | ✓
 ## ROS integration
 
 ROS integration through the
-[ros_ign](https://github.com/gazebosim/ros_ign) packages.
+[ros_gz](https://github.com/gazebosim/ros_gz) packages.
 
 Supported versions:
 

garden/ign_docker_env.md

@@ -41,9 +41,6 @@ pages:
       - name: troubleshooting
         title: Troubleshooting
         file: troubleshooting.md
-      - name: ign_docker_env
-        title: Dockerized Dev Env
-        file: ign_docker_env.md
   - name: migration_from_ignition
     title: Migration from Ignition
     file: migration_from_ignition.md

garden/index.yaml

@@ -4,7 +4,7 @@ Garden binaries are provided for Ubuntu Focal and Jammy. The
 Garden binaries are hosted in the packages.osrfoundation.org repository.
 To install all of them, the metapackage `gz-garden` can be installed.
 
-**WARNING:** `gz-garden` cannot be installed alongside gazebo-classic (eg. `gazebo11`) since both use the `gz` command line tool. Trying to install `gz-garden` on a system that already has gazebo-classic installed from binaries will cause gazebo-classic and its dependencies to be uninstalled. Currently, the workarounds for this are to install from source or to use Docker for either [`gz-garden`](https://gazebosim.org/docs/garden/ign_docker_env) or [`gazebo-classic`](https://hub.docker.com/_/gazebo) so they are not installed side-by-side on the same system.
+**WARNING:** `gz-garden` cannot be installed alongside gazebo-classic (eg. `gazebo11`) since both use the `gz` command line tool. Trying to install `gz-garden` on a system that already has gazebo-classic installed from binaries will cause gazebo-classic and its dependencies to be uninstalled. Currently, the workarounds for this are to install from source or to use Docker [`gazebo-classic`](https://hub.docker.com/_/gazebo) so they are not installed side-by-side on the same system.
 
 First install some necessary tools:
 

garden/install_ubuntu.md

@@ -5,7 +5,7 @@ WARNING: Current Windows support is experimental.
 # Binary Installation on Windows 10
 
 Most Gazebo packages are available in Windows 10 using the [conda-forge package manager](https://conda-forge.org/),
-and the Gazebo feedstock recipes can be found [here](https://github.com/conda-forge?q=libignition&type=&language=).
+and the Gazebo feedstock recipes can be found [here](https://github.com/search?q=org:conda-forge+libgz&type=code).
 
 Additionally, command line tools, the DART physics engine, and some tests are not currently supported in Windows.
 

garden/install_windows.md

@@ -14,7 +14,7 @@ For this tutorial to work correctly make sure you have the following installed:
 
 * [ROS 2 Rolling](https://docs.ros.org/en/rolling/Installation.html) or [ROS 2 Humble](https://docs.ros.org/en/humble/Installation.html)
 * [Gazebo Garden](https://gazebosim.org/docs/garden)
-* [ros_gz_bridge](https://github.com/gazebosim/ros_ign/tree/ros2#from-source)
+* [ros_gz_bridge](https://github.com/gazebosim/ros_gz/tree/ros2#from-source)
 
 ## Bidirectional communication
 
@@ -74,9 +74,7 @@ ros2 topic echo /keyboard/keypress
 This command listens to the messages sent over the `/keyboard/keypress` topic.
 
 On the Gazebo window, press on the keyboard keys and you should
-find data on the listener terminal. This is what the terminals should look like:
-
-![exchange_messages](tutorials/ros2_integration/ros_ign.png)
+find data on the listener terminal.
 
 Now it's your turn! Try to send data from ROS to Gazebo. You can also try different data types and different directions of communication.
 

garden/ros2_integration.md

@@ -6,7 +6,7 @@
 In this tutorial we will learn how to add sensors to our robot and
 to other models in our world. We will use three different sensors:
 an IMU sensor, a Contact sensor and a Lidar sensor. We will also
-learn how to launch multiple tasks with just one file using `ign_launch`.
+learn how to launch multiple tasks with just one file using `gz launch`.
 
 You can find the final world of this tutorial [here](https://github.com/gazebosim/docs/blob/master/garden/tutorials/sensors/sensor_tutorial.sdf)
 
@@ -410,10 +410,10 @@ Instead of running two different tasks from two different terminals we can make
 The launch file is an XML file. We simply define what commands will run under the `<executable>` tag.
 The first command is `gz sim sensor_tutorial.sdf` which launches the world.
 And the second command is `./build/lidar_node` which runs the `lidar_node`.
-Save the file as `sensor_launch.ign`, and then run it using the following command:
+Save the file as `sensor_launch.gzlaunch`, and then run it using the following command:
 
 ```{.sh}
-gz launch sensor_launch.ign
+gz launch sensor_launch.gzlaunch
 ```
 
 Press the play button to start the simulation. Hurray! Our robot is now moving and avoiding the wall.

garden/sensors.md

@@ -159,9 +159,9 @@ https://github.com/osrf/ogre-2.3-release
 You should be able to use Ogre 1 without any issues however. You can check if
 that's working by running a world which uses Ogre 1 instead of Ogre 2, such as:
 
-    ign gazebo -v 3 lights.sdf
+    gz sim -v 3 lights.sdf
 
-If that loads, you can continue to use Ignition with Ogre 1, just use the
+If that loads, you can continue to use Gazebo with Ogre 1, just use the
 `--render-engine ogre` option.
 
 ## Windows

garden/troubleshooting.md

@@ -1,21 +1,21 @@
-<sdf version="1.8">
+<sdf version="1.9">
   <world name="actors">
     <plugin
-      filename="libignition-gazebo-physics-system.so"
-      name="ignition::gazebo::systems::Physics">
+      filename="gz-sim-physics-system"
+      name="gz::sim::systems::Physics">
     </plugin>
     <plugin
-      filename="libignition-gazebo-sensors-system.so"
-      name="ignition::gazebo::systems::Sensors">
+      filename="libgz-sim-sensors-system.so"
+      name="gz::sim::systems::Sensors">
       <render_engine>ogre</render_engine>
     </plugin>
     <plugin
-      filename="libignition-gazebo-user-commands-system.so"
-      name="ignition::gazebo::systems::UserCommands">
+      filename="libgz-sim-user-commands-system.so"
+      name="gz::sim::systems::UserCommands">
     </plugin>
     <plugin
-      filename="libignition-gazebo-scene-broadcaster-system.so"
-      name="ignition::gazebo::systems::SceneBroadcaster">
+      filename="libgz-sim-scene-broadcaster-system.so"
+      name="gz::sim::systems::SceneBroadcaster">
     </plugin>
 
     <light type="directional" name="sun">