Gazebo physics and collision in ROS

Introduction

Gazebo physics and collision help robots move and interact with the world realistically. They make sure robots don't pass through walls or objects.

When you want your robot to avoid bumping into obstacles in a simulation.

When testing how a robot moves on different surfaces like carpet or tiles.

When simulating robot arms picking up or pushing objects.

When you want to see how objects fall or slide in the robot's environment.

When checking if your robot's sensors detect collisions correctly.

Syntax

ROS

<physics name="default_physics" type="ode">
  <gravity>0 0 -9.8</gravity>
  <max_step_size>0.001</max_step_size>
  <real_time_factor>1</real_time_factor>
</physics>

<collision name="collision_name">
  <geometry>
    <box>
      <size>1 1 1</size>
    </box>
  </geometry>
  <surface>
    <contact>
      <collide_without_contact>false</collide_without_contact>
    </contact>
  </surface>
</collision>

The <physics> tag sets the physics engine and its properties like gravity and time step.

The <collision> tag defines the shape and behavior of an object for collision detection.

Examples

Sets up the ODE physics engine with Earth gravity and a small time step for smooth simulation.

ROS

<physics name="ode_physics" type="ode">
  <gravity>0 0 -9.81</gravity>
  <max_step_size>0.002</max_step_size>
  <real_time_factor>1</real_time_factor>
</physics>

Defines a cylindrical collision shape for a robot part.

ROS

<collision name="robot_collision">
  <geometry>
    <cylinder>
      <radius>0.5</radius>
      <length>1.0</length>
    </cylinder>
  </geometry>
</collision>

This is an invalid collision because it has no shape. Gazebo will ignore it or give an error.

ROS

<collision name="empty_collision">
  <!-- No geometry defined -->
</collision>

Defines a flat floor collision shape using a plane.

ROS

<collision name="floor_collision">
  <geometry>
    <plane>
      <normal>0 0 1</normal>
    </plane>
  </geometry>
</collision>

Sample Program

This SDF file sets up a simple Gazebo world with gravity and two models: a box that can fall and a static floor. The box has a collision shape so it will collide with the floor and not fall through.

ROS

<?xml version="1.0" ?>
<sdf version="1.6">
  <world name="default">
    <physics name="default_physics" type="ode">
      <gravity>0 0 -9.8</gravity>
      <max_step_size>0.001</max_step_size>
      <real_time_factor>1</real_time_factor>
    </physics>

    <model name="box_model">
      <static>false</static>
      <link name="link">
        <collision name="box_collision">
          <geometry>
            <box>
              <size>1 1 1</size>
            </box>
          </geometry>
        </collision>
        <visual name="box_visual">
          <geometry>
            <box>
              <size>1 1 1</size>
            </box>
          </geometry>
        </visual>
        <pose>0 0 1 0 0 0</pose>
      </link>
    </model>

    <model name="floor">
      <static>true</static>
      <link name="floor_link">
        <collision name="floor_collision">
          <geometry>
            <plane>
              <normal>0 0 1</normal>
            </plane>
          </geometry>
        </collision>
        <visual name="floor_visual">
          <geometry>
            <plane>
              <normal>0 0 1</normal>
            </plane>
          </geometry>
        </visual>
        <pose>0 0 0 0 0 0</pose>
      </link>
    </model>
  </world>
</sdf>

Important Notes

Physics simulation uses CPU power; smaller time steps give smoother results but need more computing.

Collision shapes should be simple for better performance; complex shapes slow down simulation.

Common mistake: forgetting to add collision tags causes objects to pass through each other.

Summary

Gazebo physics controls how objects move and react to forces like gravity.

Collision shapes tell Gazebo where objects can touch or block each other.

Setting up physics and collision correctly makes robot simulations realistic and useful.

Practice

1. What is the main purpose of physics in Gazebo simulations?

easy

A. To define the color and texture of objects

B. To control how objects move and react to forces like gravity

C. To create user interfaces for robot control

D. To store sensor data from the robot

Solution

1. Step 1: Understand the role of physics in Gazebo

   Physics in Gazebo simulates real-world forces like gravity and friction affecting objects.

2. Step 2: Identify the correct purpose

   Physics controls object movement and reactions, not appearance or data storage.

3. Final Answer:

   To control how objects move and react to forces like gravity -> Option B

4. Quick Check:

   Physics = object movement and forces [OK]

Hint: Physics = movement and forces, not visuals or data [OK]

Common Mistakes:

• Confusing physics with visual appearance
• Thinking physics stores sensor data
• Assuming physics creates user interfaces

2. Which of the following is the correct way to define a collision shape in a Gazebo SDF file?

easy

A. 1 1 1

B. red

C. camera

D. metal

Solution

1. Step 1: Review SDF collision shape syntax

   Collision shapes use <geometry> tags with shape types like <box>, <sphere>, or <cylinder>.

2. Step 2: Identify the valid collision definition

   <collision><geometry><box><size>1 1 1</size></box></geometry></collision> correctly defines a box size inside geometry within collision tags.

3. Final Answer:

   <collision><geometry><box><size>1 1 1</size></box></geometry></collision> -> Option A

4. Quick Check:

   Collision shape = geometry + shape tags [OK]

Hint: Collision needs geometry and shape tags, not color or sensor [OK]

Common Mistakes:

• Using color or material tags inside collision
• Confusing sensors with collision shapes
• Omitting geometry tag inside collision

3. Given this SDF snippet, what will happen when the robot collides with the box?

<collision name="box_collision">
  <geometry>
    <box><size>1 1 1</size></box>
  </geometry>
</collision>

medium

A. The box will change color on collision

B. The robot will pass through the box without any effect

C. The simulation will crash due to missing physics

D. The robot will detect collision and stop or react physically

Solution

1. Step 1: Understand collision shape effect

   The collision shape defines where objects physically interact and block each other.

2. Step 2: Predict behavior on collision

   When the robot hits the box collision shape, physics will cause it to stop or react realistically.

3. Final Answer:

   The robot will detect collision and stop or react physically -> Option D

4. Quick Check:

   Collision shape causes physical interaction [OK]

Hint: Collision shapes cause physical blocking, not visual changes [OK]

Common Mistakes:

• Thinking collision changes color
• Assuming robot passes through objects with collision
• Believing simulation crashes without physics tag

4. You wrote this collision tag in your Gazebo model but the robot passes through the object. What is the likely error?

<collision>
  <geometry>
    <sphere><radius>0.5</radius></sphere>
  </geometry>
</collision>

medium

A. The physics engine is not enabled or configured properly

B. The collision tag is missing a name attribute

C. The sphere radius is too small to detect collision

D. The geometry tag should be outside the collision tag

Solution

1. Step 1: Check collision tag correctness

   The collision tag syntax is correct and includes geometry with a sphere shape.

2. Step 2: Identify common cause of passing through objects

   If physics is disabled or misconfigured, collisions won't be processed, causing objects to pass through.

3. Final Answer:

   The physics engine is not enabled or configured properly -> Option A

4. Quick Check:

   Physics engine must be active for collisions [OK]

Hint: Collision needs physics engine enabled to work [OK]

Common Mistakes:

• Thinking missing name attribute breaks collision
• Assuming small radius disables collision
• Placing geometry outside collision tag

5. You want to simulate a robot pushing a box realistically in Gazebo. Which combination of settings is best to achieve this?

hard

A. Only define visual shapes and manually move the box in code

B. Disable physics engine, use only visual shapes for robot and box

C. Enable physics engine with friction, define collision shapes for both robot and box

D. Use collision shapes but set friction to zero in physics settings

Solution

1. Step 1: Understand realistic pushing requires physics and collision

   Physics engine simulates forces like friction and collision shapes define contact areas.

2. Step 2: Evaluate options for realistic interaction

   Enable physics engine with friction, define collision shapes for both robot and box enables physics with friction and collision shapes, allowing realistic pushing behavior.

3. Step 3: Reject options disabling physics or friction

   Disabling physics or friction or using only visuals prevents realistic physical interaction.

4. Final Answer:

   Enable physics engine with friction, define collision shapes for both robot and box -> Option C

5. Quick Check:

   Physics + friction + collision = realistic pushing [OK]

Hint: Physics + friction + collision shapes = realistic object interaction [OK]

Common Mistakes:

• Disabling physics engine expecting realistic forces
• Setting friction to zero for pushing
• Using only visual shapes without collision