Occupancy grid map concept in ROS - Performance & Optimization

Performance: Occupancy grid map concept

MEDIUM IMPACT

This concept affects how quickly a robot can update and render its environment map, impacting real-time navigation and sensor data processing.

Updating the occupancy grid map with sensor data

ROS

for each cell within sensor range:
    update occupancy probability based on sensor reading

Limits updates to relevant cells only, reducing CPU usage and speeding up map refresh.

📈 Performance Gainreduces processing time by 80% on typical sensor ranges

Updating the occupancy grid map with sensor data

ROS

for each cell in the entire grid:
    update occupancy probability based on sensor reading

Updating every cell regardless of sensor range causes unnecessary computations and slows down processing.

📉 Performance Costblocks processing for hundreds of milliseconds on large grids

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Update entire grid every cycle	N/A	N/A	High CPU load delays rendering	[X] Bad
Update only cells in sensor range	N/A	N/A	Lower CPU load, smoother updates	[OK] Good

Rendering Pipeline

Sensor data triggers occupancy updates which modify grid cells. The updated grid is then used for path planning and visualization.

→Data Processing

→Map Update

→Visualization Rendering

⚠️ BottleneckMap Update stage due to large grid size and frequent updates

Optimization Tips

1Only update grid cells affected by new sensor data.

2Use efficient data structures to store and access grid cells.

3Balance grid resolution with processing capabilities to maintain real-time updates.

Performance Quiz - 3 Questions

What is the main performance issue when updating an occupancy grid map inefficiently?

A Rendering the map with colors

B Using a small grid size

C Updating all grid cells regardless of sensor data range

D Using multiple sensors

DevTools: rosbag play with rqt_graph and rqt_plot

How to check: Record sensor and map update topics, then replay and observe CPU usage and update frequency in rqt_plot.

What to look for: Look for spikes in CPU usage and delays in map update frequency indicating inefficient updates.

Practice

1.

What does an occupancy grid map represent in ROS?

easy

A. A grid showing which areas are free, occupied, or unknown

B. A list of robot commands to move in space

C. A 3D model of the robot's shape

D. A sensor data stream from the robot's camera

Solution

1. Step 1: Understand the purpose of occupancy grid maps

   Occupancy grid maps divide space into small cells to mark if they are free, occupied, or unknown.

2. Step 2: Match the description to the options

   A grid showing which areas are free, occupied, or unknown correctly describes this as a grid showing cell states. Other options describe unrelated concepts.

3. Final Answer:

   A grid showing which areas are free, occupied, or unknown -> Option A

4. Quick Check:

   Occupancy grid = space divided into free/occupied/unknown cells [OK]

Hint: Occupancy grid = map of free or blocked spaces [OK]

Common Mistakes:

• Confusing occupancy grid with robot commands
• Thinking it is a 3D robot model
• Mixing it up with raw sensor data

2.

Which data type correctly represents the occupancy grid map data in ROS?

nav_msgs::OccupancyGrid map;
// What type is map.data?

easy

A. bool[][]

B. std::string

C. std::vector<int8_t>

D. float[]

Solution

1. Step 1: Recall the ROS message type for occupancy grid data

   The map.data field is a list of signed 8-bit integers representing cell states.

2. Step 2: Match the data type to the options

   std::vector<int8_t> matches the expected type. Other options do not fit the ROS message definition.

3. Final Answer:

   std::vector<int8_t> -> Option C

4. Quick Check:

   map.data type = std::vector<int8_t> [OK]

Hint: Occupancy data uses vector of int8_t in ROS [OK]

Common Mistakes:

• Assuming map.data is a string or float array
• Thinking it is a 2D bool array
• Confusing with sensor_msgs data types

3.

Given this snippet in ROS Python:

grid = [0, 100, -1, 0]
free_cells = sum(1 for cell in grid if cell == 0)
occupied_cells = sum(1 for cell in grid if cell == 100)
unknown_cells = sum(1 for cell in grid if cell == -1)
print(f"Free: {free_cells}, Occupied: {occupied_cells}, Unknown: {unknown_cells}")

What will be printed?

medium

A. Free: 1, Occupied: 1, Unknown: 2

B. Free: 1, Occupied: 2, Unknown: 1

C. Free: 2, Occupied: 0, Unknown: 2

D. Free: 2, Occupied: 1, Unknown: 1

Solution

1. Step 1: Count free cells (value 0) in the list

   grid has two zeros at positions 0 and 3, so free_cells = 2.

2. Step 2: Count occupied cells (value 100) and unknown cells (value -1)

   One 100 at position 1 (occupied_cells = 1), one -1 at position 2 (unknown_cells = 1).

3. Final Answer:

   Free: 2, Occupied: 1, Unknown: 1 -> Option D

4. Quick Check:

   Count values 0, 100, -1 correctly [OK]

Hint: Count each cell value carefully to avoid off-by-one errors [OK]

Common Mistakes:

• Miscounting zeros or other values
• Confusing unknown (-1) with free (0)
• Mixing occupied (100) with unknown (-1)

4.

Identify the error in this ROS Python code snippet that tries to update an occupancy grid cell:

map_data = [0, 0, 0, 0]
index = 2
map_data[index] = 100
print(map_data)

Why might this code fail in a real ROS occupancy grid update?

medium

A. map_data should be updated via the OccupancyGrid message, not a plain list

B. map_data is a tuple and cannot be changed

C. Index 2 is out of range for map_data

D. 100 is not a valid occupancy value

Solution

1. Step 1: Check data type and mutability

   map_data is a list here, so assignment works in Python, no error from mutability.

2. Step 2: Understand ROS occupancy grid update rules

   In ROS, occupancy grid data must be updated through the OccupancyGrid message interface, not by directly modifying a local list copy.

3. Final Answer:

   map_data should be updated via the OccupancyGrid message, not a plain list -> Option A

4. Quick Check:

   Update occupancy grid via ROS message, not local list [OK]

Hint: Update occupancy grid through ROS message, not local list [OK]

Common Mistakes:

• Assuming direct list change updates ROS map
• Thinking index 2 is invalid
• Believing 100 is invalid occupancy value

5.

You want to create a 5x5 occupancy grid map in ROS where the center cell is occupied (value 100), edges are unknown (-1), and others are free (0). Which Python code correctly creates the data list for this map?

# Options:
# A
# data = [100 if i == 12 else -1 if i % 5 == 0 or i % 5 == 4 else 0 for i in range(25)]

# B
# data = [0]*25
# data[12] = 100
# for i in range(25):
#     if i % 5 == 0 or i % 5 == 4 or i < 5 or i > 19:
#         data[i] = -1

# C
# data = [-1]*25
# data[12] = 100
# for i in range(25):
#     if i % 5 != 0 and i % 5 != 4 and 5 <= i <= 19:
#         data[i] = 0

# D
# data = [0 if i != 7 else 100 for i in range(25)]
# for i in range(25):
#     if i % 5 == 0 or i % 5 == 4 or i < 5 or i > 19:
#         data[i] = -1

hard

A. Creates data with center 100, edges -1, others 0 in one list comprehension

B. Starts with all 0s, sets center 100, then sets edges to -1 in a loop

C. Starts with all -1s, sets center 100, then sets inner cells to 0 in a loop

D. Starts with zeros except center 100, then sets edges -1 in a loop

Solution

1. Step 1: Understand the map layout requirements

   Center cell (index 12) = 100, edges = -1, others = 0 in a 5x5 grid (indexes 0-24).

2. Step 2: Analyze each option's logic

   Starts with all 0s, sets center to 100, then sets edges to -1 in a loop, matching requirements exactly.

3. Final Answer:

   Starts with all 0s, sets center 100, then sets edges to -1 in a loop -> Option B

4. Quick Check:

   Initialize edges as -1, center 100, inner cells 0 [OK]

Hint: Initialize edges first, then set center and free cells [OK]

Common Mistakes:

• Confusing edge indexes with inner cells
• Overwriting center cell after setting edges
• Using incorrect conditions for edges