Gazebo physics and collision in ROS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the physics engine in a Gazebo world file.

ROS

<physics name="default_physics" type="[1]">
  <max_step_size>0.001</max_step_size>
  <real_time_factor>1</real_time_factor>
</physics>

Drag options to blanks, or click blank then click option'

Aode

Bbullet

Cdart

Dsimbody

Attempts:

3 left

💡 Hint

Common Mistakes

Using a physics engine name not supported by the Gazebo version.

Leaving the type attribute empty.

The type attribute defines the physics engine Gazebo uses. 'ode' is the default physics engine.

2fill in blank

medium

Complete the SDF snippet to enable collision detection for a link.

ROS

<link name="wheel_link">
  <collision name="wheel_collision">
    <geometry>
      <cylinder>
        <radius>0.1</radius>
        <length>0.05</length>
      </cylinder>
    </geometry>
    <[1]>
      <surface>
        <contact>
          <collide_without_contact>true</collide_without_contact>
        </contact>
      </surface>
    </[1]>
  </collision>
</link>

Drag options to blanks, or click blank then click option'

Avisual

Bcollision

Ccontact

Dsensor

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'collision' tag inside itself, which is invalid.

Confusing 'visual' with collision properties.

The contact tag inside surface defines collision contact properties.

3fill in blank

hard

Fix the error in the Gazebo plugin snippet to correctly subscribe to contact sensor messages.

ROS

#include <gazebo/gazebo.hh>
#include <gazebo/sensors/sensors.hh>

void OnContact(const gazebo::msgs::Contacts &contacts) {
  // Process contacts
}

void Load() {
  auto sensor = gazebo::sensors::SensorManager::Instance()->GetSensor("contact_sensor");
  sensor->[1](std::bind(&OnContact, std::placeholders::_1));
}

Drag options to blanks, or click blank then click option'

AConnectNewMessage

BConnectUpdated

CSubscribe

DListen

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Subscribe' which is not a Gazebo sensor method.

Using 'ConnectUpdated' which is for different event types.

The ConnectNewMessage method subscribes to new sensor messages in Gazebo plugins.

4fill in blank

hard

Fill both blanks to create a Gazebo model plugin that disables gravity and sets friction parameters.

ROS

#include <gazebo/gazebo.hh>

class [1] : public gazebo::ModelPlugin {
public:
  void Load(gazebo::physics::ModelPtr model, sdf::ElementPtr sdf) override {
    model->SetGravityMode([2]);
    auto link = model->GetLink("base_link");
    if (link) {
      auto surface = link->GetCollision(0)->GetSurface();
      surface->FrictionPyramid()->SetMuPrimary(1.0);
      surface->FrictionPyramid()->SetMuSecondary(1.0);
    }
  }
};

Drag options to blanks, or click blank then click option'

ADisableGravityPlugin

BEnableGravityPlugin

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Setting gravity mode to true disables gravity.

Using a generic class name unrelated to gravity.

The plugin class name can be anything descriptive. To disable gravity, SetGravityMode(false) is used.

5fill in blank

hard

Fill all three blanks to define a Gazebo SDF collision element with a box geometry and set its friction coefficients.

ROS

<collision name="box_collision">
  <geometry>
    <box>
      <size>[1] [2] [3]</size>
    </box>
  </geometry>
  <surface>
    <friction>
      <ode>
        <mu>0.8</mu>
        <mu2>0.6</mu2>
      </ode>
    </friction>
  </surface>
</collision>

Drag options to blanks, or click blank then click option'

A1.0

B0.5

C0.3

D2.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using zero or negative values for size.

Providing only one or two size values instead of three.

The size tag requires three dimensions: length, width, and height. Here, 2.0, 0.5, and 0.3 are valid sizes in meters.

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