Andino Gazebo Simulation

:clipboard: Description

This package provides a simulation environment for Andino in Gazebo Fortress relying on ros_gz to integrate it with ROS 2.

:clamp: Platforms

• ROS 2: Humble Hawksbill
• OS:
  • Ubuntu 22.04 Jammy Jellyfish
• Gazebo:
  • Fortress

:inbox_tray: Installation

1. Clone this repository

git clone git@github.com:ekumenlabs/andino_gz.git

1. Set up docker environment: Refer to docker readme

Once the container is running and dependencies have been installed you can proceed to package building.

:package: Build

The package contains some dependencies that must be installed in order to build it:

rosdep install --from-paths src -i -y

Then build the package and source the install workspace. To do so run the following commands:

colcon build
source install/setup.bash

:rocket: Usage

Andino simulation

Once the package is built and sourced, you can start a simulation.

  ros2 launch andino_gz andino_gz.launch.py
  

Note: You can use world_name flag to indicate other world to use. (For example: depot.sdf(default), office.sdf, populated_office.sdf, empty.sdf)

By default the ros bridge and rviz are initialized. In case you prefer to disable any of those you can do it via its flags:

  ros2 launch andino_gz andino_gz.launch.py ros_bridge:=False rviz:=False
  

To see a complete list of available arguments for the launch file do:

  ros2 launch andino_gz andino_gz.launch.py --show-args
  

Using a different world:

  ros2 launch andino_gz andino_gz.launch.py world_name:=populated_office.sdf
  

Make sure to review the required topics using ign topics and ros2 topic CLI tools. Also, consider using looking at the translation entries under andino_gz/config/bridge_config.yaml.

:robot::robot::robot: Multi robot simulation

This simulation also supports multi-robot simulation.

  ros2 launch andino_gz andino_gz.launch.py robots:="
       andino1={x: 0.0, y: 0.0, z: 0.1, yaw: 0.};
       andino2={x: -0.4, y: 0.1, z: 0.1, yaw: 0.};
       andino3={x: -0.4, y: -0.1, z: 0.1, yaw: 0.};
       andino4={x: -0.8, y: 0.2, z: 0.1, yaw: 0.};
       andino5={x: -0.8, y: -0.2, z: 0.1, yaw: 0.};
       andino6={x: -0.8, y: 0.0, z: 0.1, yaw: 0.};"
  

• Note1: You can add as many Andino as you want.
• Note2: If enabling Nav2(Using nav2:=True) try first with 2 robots and see how they perform in your system before using more robots.

The launch file is in charge of:

• Start Gazebo simulator with a defined world (See ‘–world_name’ flag)
• Spawn as many robots as commanded.
• Launch ros bridge for each robot.
• Launch Rviz visualization for each robot.

The simulation allows you to spawn as many robots as you want via the --robots flags. For that, you can pass the information of the robots in some YAML format via ROS2 cli:

    <robot_name>={x: 0.0, y: 0.0, yaw: 0.0, roll: 0.0, pitch: 0.0, yaw: 0.0};
  

• Note1: A ROS Namespace is pushed for each robot so all the topics and nodes are called the same with a difference of a <robot_name> prefix.
• Note2: For RViz2 to work with the ROS namespace that is pushed, one has to ensure that no absolute topics are being used.

:compass: Navigation

1. Run the simulation passing the nav2 flag.

    ros2 launch andino_gz andino_gz.launch.py nav2:=True
    

As before, you can launch as many robots as you want, for example launching two:

    ros2 launch andino_gz andino_gz.launch.py nav2:=True robots:="andino1={x: 0.0, y: 0.0, z: 0.1, yaw: 0.};andino2={x: 1.0, y: 0.0, z: 0.1, yaw: 0.};" 
    

Once Gazebo window pops up, play the simulation using the gui.

**Important!**:
  -  When using `nav2` flag, the `map` must match the selected `world`. For example:
     -  For `depot.sdf` world, the map need to be `depot`:

            ros2 launch andino_gz andino_gz.launch.py nav2:=True world_name:=depot.sdf map:=depot
            

        Typically, as this is the default world-map, there is no need to indicate them.
     -  For `office.sdf` and `populated_office.sdf` worlds, the map need to be `office`:

            ros2 launch andino_gz andino_gz.launch.py nav2:=True world_name:=office.sdf map:=office
            

1. An RViz window will be spawned for each robot so it can be controlled independently. Use 2D Pose Estimate to pass a hint to AMCL where is the initial point

   Note you have to do it per robot, namely, per RViz window.

   

2. Send the desired goal using Nav2 Goal

   

:world_map: SLAM

1. Run simulation with ros bridge and RViz.

    ros2 launch andino_gz andino_gz.launch.py
    

1. Run slam toolbox

    ros2 launch andino_gz slam_toolbox_online_async.launch.py
    

Configuration can be forwarded to the `slam_toolbox_node`. By default, the configuration parameters are obtained from [andino's configuration file](https://github.com/Ekumen-OS/andino/blob/humble/andino_slam/config/slam_toolbox_online_async.yaml). In case a custom file is wanted to be passed, simply use the launch file argument for indicating the path to a new file.

    ros2 launch andino_gz slam_toolbox_online_async.launch.py slams_param_file:=<my_path>
    

1. Visualize in RViz: Add map panel to RViz and see how the map is being generated.

:raised_hands: Contributing

Issues or PRs are always welcome! Please refer to CONTRIBUTING doc.

Code development

Note that a Docker folder is provided for easy setting up the workspace.

Contributing

The contributing guidelines are based on Andino project’s guidelines.

Contributing to andino_gz

The following is a set of guidelines for contributing to andino_gz project. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.

Code of Conduct

This project and everyone participating in it is governed by the CODE OF CONDUCT. By participating, you are expected to uphold this code.

How to Contribute

Reporting Bugs

Before Submitting a Bug Report

1. Determine the repository which should receive the problem.
2. Search the repository’s issues to see if the same or similar problem has been opened. If it has and the issue is still open, then add a comment to the existing issue. Otherwise, create a new issue.

How to Submit a Good Bug Report

Create an issue on the repository that is related to your bug, explain the problem, and include additional details to help maintainers reproduce the problem. Refer to the `Short, Self Contained, Correct (Compilable), Example Guide as well as the following tips:

• Use a clear and descriptive title for the issue to identify the problem.
• Describe the exact steps which reproduce the problem in as many details as possible. When listing steps, don’t just say what you did, but explain how you did it.
• Provide specific examples to demonstrate the steps. Include links to files or projects, or copy/pasteable snippets, which you use in those examples.
• Describe the behavior you observed after following the steps and point out what exactly is the problem with that behavior.
• Explain which behavior you expected to see instead and why.
• Include screenshots and animated GIFs which show you following the described steps and clearly demonstrate the problem.
• If the problem wasn’t triggered by a specific action, describe what you were doing before the problem happened and share more information using the guidelines below.

Provide more context by answering these questions:

• Did the problem start happening recently (e.g. after updating to a new version) or was this always a problem?
• If the problem started happening recently, can you reproduce the problem in an older version? What’s the most recent version in which the problem doesn’t happen?
• Can you reliably reproduce the issue? If not, provide details about how often the problem happens and under which conditions it normally happens.

Include details about your configuration and environment:

• Which version of andino_gz are you using??
• What’s the name and version of the OS you’re using?
• Are you running andino_gz using the provided docker container? See docker.
• Are you running andino_gz in a virtual machine? If so, which VM software are you using and which operating systems and versions are used for the host and the guest?

Suggesting Enhancements

This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions.

Before creating enhancement suggestions, please check before-submitting-a-bug-report as you might find out that you don’t need to create one. When you are creating an enhancement suggestion, please include as many details as possible. When filling in the issue form for an enhancement suggestion, include the steps that you imagine you would take if the feature you’re requesting existed.

Before Submitting An Enhancement Suggestion

• Check if you’re using the latest software version. A more recent version may contain your desired feature.
• Determine which repository the enhancement should be suggested in
• Perform a cursory search to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.

How Do I Submit A (Good) Enhancement Suggestion

Enhancement suggestions are tracked as GitHub issues. After you’ve determined which repository your enhancement suggestion is related to, create an issue on that repository and provide the following information:

• Use a clear and descriptive title for the issue to identify the suggestion.
• Provide a step-by-step description of the suggested enhancement in as many details as possible.
• Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks.
• Describe the current behavior and explain which behavior you expected to see instead and why.
• Include screenshots and animated GIFs which show you following the described steps and clearly demonstrate the problem.
• Explain why this enhancement would be useful to most users and isn’t something that can or should be implemented as a separate application.
• Specify which version of andino_gz you’re using.
• Specify the name and version of the OS you’re using.

Contributing Code

We follow a development process designed to reduce errors, encourage collaboration, and make high quality code. Review the following to get acquainted with this development process.

#. Read the reporting_bugs and suggesting_enhancements sections first.

#. Fork the andino_gz package you want to contribute to. This will create your own personal copy of the package. All of your development should take place in your fork.

• An important thing to do is create a remote pointing to the upstream remote repository. This way, you can always check for modifications on the original repository and always keep your fork repository up to date.

#. Work out of a new branch, one that is not a release / main branch. This is a good habit to get in, and will make your life easier.

#. Write your code. To remember:

• Look at the existing code and try to maintain the existing style and pattern as much as possible
• Always keep your branch updated with the original repository

Process

All Andino team members actively:

• Watch all Andino-related repositories to receive email notifications of new issues / pull requests
• Provide feedback to issues as soon as possible

• Review pull requests as soon as possible

  • Team members can review pull requests already under review or approved
  • Team members can provide some feedback without doing a full review

Pull requests can be merged when:

• They have at least 1 approval from a member of the core team
• There are no unresolved comments
• CI is passing

• Developer Certificate of Origin(DCO) check is passing

  • DCO is a declaration of ownership, basically saying that you created the contribution and that it is suitable to be covered under an open source license (not proprietary).
  • All you have to do is end your commit message with Signed-off-by: Your Full Name your.name@email.com
  • If your user.name and user.email configurations are set up in git, then you can simply run git commit -s to have your signature automatically appended.

Merging strategy:

• For internal contributions, give the original author some time to hit the merge button themselves / check directly with them if it’s ok to merge.
• Default to “squash and merge”
  • Review the pull request title and reword if necessary since this will be part of the commit message.
  • Make sure the commit message concisely captures the core ideas of the pull request and contains all authors’ signatures.