How Is Accuracy Measured in Computer Vision? False Positives and False Negatives

Why a single accuracy figure is not enough — and what to measure instead.

5 min readBy the Hype Vision engineering team

A claim such as “98% accuracy” does not help you decide unless you know what was measured, on which data and under which conditions. To know whether a system works on your site, measure two kinds of error separately.

Two kinds of error

TermMeaningEffect on site
False positiveAlert without a real eventAlarm fatigue; system gets ignored
False negativeReal event without an alertRisk goes unnoticed
True positiveEvent correctly detectedThe actual value of the system

Precision and recall

  • Precision: the share of alerts that are real. Low precision floods the team with false alarms.
  • Recall: the share of real events that are caught. Low recall means risk is missed.

There is a trade-off: lowering the threshold catches more events but raises false alarms. The right balance depends on the use case — missing a fire is worse than missing a single PPE violation.

Validating on your own footage

  1. Select footage from the pilot cameras for a defined period.
  2. Have people mark the real events.
  3. Compare system events against those marks.
  4. Report true detections, false alarms and misses per camera.
  5. Adjust rules and thresholds, then measure again.

When you see an accuracy figure in a proposal, ask: on what data, under which camera conditions, and how were false alarms and misses measured separately?

Not sure what is feasible on your site? Send a few camera frames and your use case.

Evaluate your cameras

Frequently asked questions

Does accuracy change over time?

It can, if camera positions, lighting or processes change. Periodic checks and recalibration are recommended.