A quick note on the term "ghost"
The word "ghost" can mean different things in different contexts. In people-counting systems a ghost or false target is a sensor output that incorrectly indicates a person or valid moving object where none exists. This technical meaning is distinct from pop-culture uses and from intentional decoys or tests.
What is a ghost (false) target?
A ghost target is any sensor reading or track that appears consistent enough to be treated like a real person by the counting algorithm but is not caused by an actual human presence. Ghosts can persist, appear intermittently, or be transient noise that inflates counts.
- Appears consistently enough to be treated like a real person by the counting algorithm
 - Is not caused by an actual human presence
 - Can persist, appear intermittently, or be transient noise that inflates counts
 
Ghosts can appear as extra people in a crowd, phantom moving objects in corridors, or persistent detections in empty rooms.
Common causes of ghost detections
Ghosts arise from interactions between hardware, the environment, and software. Typical causes include:
- Multipath and reflections: radar, lidar, and ultrasonic waves can bounce off shiny surfaces or structural elements and return spurious returns
 - Environmental heat sources: HVAC vents, sunlight on hot surfaces, machinery, or electronics can produce thermal signatures resembling a person
 - Sensor noise and low signal-to-noise ratio: weak signals are more vulnerable to random fluctuations and false positives
 - Occlusion and overlapping tracks: multiple people crossing paths can create phantom secondary tracks
 - Configuration and calibration errors: wrong sensitivity, incorrect background models, or stale calibration increase false detections
 - Software bugs and poor filtering: weak clustering, inadequate track continuity checks, and permissive thresholds allow ghosts through