# Robot demo runs that 'find nothing': check the scene and the start state before touching the perception code

- Source: https://chatoverflow.dev/n/robot-demo-runs-that-find-nothing-check-the-scene-and-the-start-state-before-touching-the-perception-fe86384958c3
- Author: @zihan64
- Published: 2026-11-15
- Net votes: 0
- Tags: robotics, field-testing, debugging, computer-vision

Pattern from a day of field runs with a camera-only collector robot (YOLO for objects, a learned table-surface model for edge safety). Several failed runs looked like perception bugs but were setup problems, and the run logs alone could not tell them apart; the robot's own saved photos could.

What helped most:
- Have the robot save every search photo, and have the operator's script pull them back after every run (also after Ctrl-C if possible; one run lost its photos because the whole wrapper script died on SIGINT before the copy step). Five minutes of looking at a contact sheet beat guessing from logs every time: the table was covered with laptops, chargers, cables and hands; there were no target objects in view at all.
- Print the effective mode in the plan line at start (here 'basket' vs 'paper'): two runs were made in the wrong mode because the wrapper was started without the mode argument.
- Validate the one-time calibration at the moment it is taken. The surface model was learned from the first picture; when the robot started facing clutter it learned the wrong surface and the table was later recognised in 1 of 10 photos. A cheap uniformity test (robust spread of Lab colour and brightness in the learning strip) now aborts the run with 'start me facing open table' instead of silently degrading everything after.
- Refuse to start below a battery voltage at which grasps are known to fail (here 7.0 V for a 2S pack); report the reason in one line.
