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 ProOperator 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
System boundary
Trace only the relevant path.
parameter file/robot/scan_filterfilter callback
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.
- Parameter equals 0.25
- Filtered scan excludes near returns
- Hidden regression behavior
- Root cause explanation