Guided beta caseProbeginnerSensor source
The costmap ignores visible scans
Restore obstacle marking without remapping the driver globally.
Pairs with Sensor layers and clearing in Nav2 Incident Response. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
RViz shows `/scan_filtered`, but the local costmap remains empty.
Ubuntu 24.04, ROS 2 Jazzy, Nav2, Gazebo Harmonic, warehouse mission simulator
System boundary
Trace only the relevant path.
/scan_filteredobstacle layer sourcelocal costmap
How this lab works
You diagnose it — no command list.
Open the repair workspace and gather your own evidence in a real terminal. No diagnostic commands are handed to you — finding the fault is the exercise. Stuck? Progressive hints unlock inside the workspace.
Verification
Your repair must pass more than the visible symptom.
- Obstacle cells appear
- Filtered scan remains the only source
- Hidden regression behavior
- Root cause explanation