Link element (visual, collision, inertial) in ROS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a visual element inside a link in URDF.

ROS

<link name="base_link">
  <visual>
    <geometry>
      <[1] radius="0.1" />
    </geometry>
  </visual>
</link>

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

Amesh

Bbox

Csphere

Dcylinder

Attempts:

3 left

💡 Hint

Common Mistakes

Using box or cylinder instead of sphere for a round shape.

The sphere tag defines a spherical visual geometry with a radius attribute.

2fill in blank

medium

Complete the code to specify the mass of the inertial element in URDF.

ROS

<link name="arm_link">
  <inertial>
    <mass value="[1]" />
  </inertial>
</link>

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

A1.2

B0.5

C2.0

D5.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using zero or negative values for mass.

The mass tag's value attribute sets the mass of the link in kilograms.

3fill in blank

hard

Fix the error in the collision element by completing the geometry tag correctly.

ROS

<link name="wheel_link">
  <collision>
    <geometry>
      <[1] length="0.2" radius="0.05" />
    </geometry>
  </collision>
</link>

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

Abox

Bcylinder

Csphere

Dmesh

Attempts:

3 left

💡 Hint

Common Mistakes

Using sphere with length attribute causes errors.

The cylinder tag requires both length and radius attributes, suitable for wheel collision shapes.

4fill in blank

hard

Fill both blanks to define an inertial origin and inertia matrix correctly.

ROS

<link name="gripper_link">
  <inertial>
    <origin xyz="[1]" rpy="0 0 0" />
    <inertia ixx="[2]" ixy="0" ixz="0" iyy="0.01" iyz="0" izz="0.01" />
  </inertial>
</link>

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

A0 0 0

B0.02

C0.1

D0 0 0.1

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-numeric strings for inertia values.

Incorrect xyz format with commas.

The origin xyz attribute sets the position offset; 0 0 0 means no offset. The ixx value is part of the inertia matrix and must be a positive float.

5fill in blank

hard

Fill all three blanks to define a visual mesh with pose and scale in a link.

ROS

<link name="sensor_link">
  <visual>
    <origin xyz="[1]" rpy="0 0 0" />
    <geometry>
      <mesh filename="[2]" scale="[3]" />
    </geometry>
  </visual>
</link>

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

A0 0 0.05

Bpackage://robot_description/meshes/sensor.dae

C1 1 1

D0 0 0

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect file paths for mesh.

Wrong scale format or missing scale.

The origin xyz sets the mesh position offset. The filename attribute points to the mesh file path. The scale attribute adjusts the mesh size uniformly.

Practice

1.

What is the main purpose of the visual element inside a link in ROS?

easy

A. To define how the robot part looks in simulation or visualization

B. To specify the physical mass of the robot part

C. To detect collisions with other objects

D. To control the robot's joint movements

Solution

1. Step 1: Understand the role of visual in a link

   The visual element describes the shape and appearance of the robot part for display purposes.

2. Step 2: Differentiate from other elements

   collision is for detecting bumps, and inertial is for physics like mass. Only visual affects appearance.

3. Final Answer:

   To define how the robot part looks in simulation or visualization -> Option A

4. Quick Check:

   visual = appearance [OK]

Hint: Visual = looks, Collision = bump, Inertial = mass [OK]

Common Mistakes:

• Confusing visual with collision for physical interaction
• Thinking inertial controls appearance
• Assuming visual affects robot movement

2.

Which of the following is the correct syntax to define an inertial element inside a link in URDF?

<link name="arm">
  <inertial>
    <mass value="5.0" />
    <origin xyz="0 0 0" />
  </inertial>
</link>

easy

A. Mass is defined inside inertial with a value attribute

B. Mass is defined inside visual with a value attribute

C. Mass is defined inside collision with a mass tag

D. Mass is defined as an attribute of link directly

Solution

1. Step 1: Check URDF inertial syntax

   The inertial element contains a mass tag with a value attribute specifying the mass.

2. Step 2: Verify other options

   Mass is not part of visual or collision, nor is it an attribute of link.

3. Final Answer:

   Mass is defined inside inertial with a value attribute -> Option A

4. Quick Check:

   Mass inside inertial = correct syntax [OK]

Hint: Mass always goes inside inertial with value attribute [OK]

Common Mistakes:

• Placing mass inside visual or collision elements
• Using mass as an attribute of link
• Omitting the value attribute in mass tag

3.

Given this URDF snippet, what will happen in simulation regarding collisions?

<link name="wheel">
  <visual>
    <geometry><cylinder radius="0.1" length="0.05" /></geometry>
  </visual>
  <collision>
    <geometry><sphere radius="0.1" /></geometry>
  </collision>
</link>

medium

A. Simulation will crash due to shape mismatch

B. Collision detection uses the cylinder shape matching the visual

C. Collision detection uses a sphere shape, different from the visual cylinder

D. No collision detection will occur because shapes differ

Solution

1. Step 1: Identify visual and collision shapes

   The visual shape is a cylinder, but the collision shape is a sphere with radius 0.1.

2. Step 2: Understand collision behavior

   Collision uses the collision geometry, so it will detect collisions as a sphere, ignoring the visual cylinder shape.

3. Final Answer:

   Collision detection uses a sphere shape, different from the visual cylinder -> Option C

4. Quick Check:

   Collision shape overrides visual for bump detection [OK]

Hint: Collision shape controls bump detection, not visual shape [OK]

Common Mistakes:

• Assuming collision uses visual shape automatically
• Thinking shape mismatch causes simulation crash
• Believing no collision happens if shapes differ

4.

Identify the error in this URDF link definition:

<link name="base">
  <inertial>
    <mass value="-2.0" />
    <origin xyz="0 0 0" />
  </inertial>
  <visual>
    <geometry><box size="1 1 1" /></geometry>
  </visual>
</link>

medium

A. Origin element is missing required attributes

B. Mass value cannot be negative in inertial element

C. Box size must be three equal numbers

D. Visual element cannot be inside link

Solution

1. Step 1: Check mass value validity

   Mass must be positive because negative mass is physically impossible and invalid in URDF.

2. Step 2: Verify other elements

   Box size can be any three numbers, origin xyz is valid, and visual is correctly inside link.

3. Final Answer:

   Mass value cannot be negative in inertial element -> Option B

4. Quick Check:

   Mass > 0 required in inertial [OK]

Hint: Mass must be positive, never negative [OK]

Common Mistakes:

• Allowing negative mass values
• Thinking box size must be equal dimensions
• Believing visual cannot be inside link

5.

You want to simulate a robot arm where the visual shape is a complex mesh, but collision detection should be simpler for performance. How should you define the link elements?

hard

A. Use the same detailed mesh in both visual and collision

B. Omit the collision element to improve performance

C. Use a simple shape in visual and a detailed mesh in collision

D. Use a detailed mesh in visual and a simple primitive shape in collision

Solution

1. Step 1: Understand visual vs collision roles

   Visual defines appearance, so use the complex mesh here for realistic look.

2. Step 2: Optimize collision for performance

   Collision should be simpler to reduce computation, so use a primitive shape like box or sphere.

3. Step 3: Avoid omitting collision

   Omitting collision disables bump detection, which is usually undesirable.

4. Final Answer:

   Use a detailed mesh in visual and a simple primitive shape in collision -> Option D

5. Quick Check:

   Visual = detail, Collision = simple for speed [OK]

Hint: Visual = detail, collision = simple shape for speed [OK]

Common Mistakes:

• Using complex mesh for collision causing slow simulation
• Skipping collision element losing bump detection
• Using simple visual but complex collision shape