Pricing
00
In productionProbeginnerParameter YAML

The parameter loads under the wrong node

Restore scan filtering without renaming the deployed node.

Pairs with Parameters and launch in ROS 2 Systems Debugging. Read the concept first, then diagnose it here.

Unlock this lab with Pro

Operator report

`min_range` remains at 0.0 although the YAML file specifies 0.25.

Ubuntu 24.04, ROS 2 Jazzy, Python and C++ nodes, browser telemetry workspace

01

System boundary

Trace only the relevant path.

3 nodes
  1. 01parameter file→
  2. 02/robot/scan_filter→
  3. 03filter callbackOUT
02

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.

03

Verification

Pass more than the visible symptom.

4 checks
  • Parameter equals 0.25
  • Filtered scan excludes near returns
  • Hidden regression behavior
  • Root cause explanation