Lesson 5 of 2245 minutes

Sensors and Measurement Uncertainty

Start with the lesson question, connect the representations, and test the model with evidence.

sensorsmeasurement uncertaintycalibrationbiasnoiselatency

Learning objectives

  • Explain the responsibilities of sensors, actuators, compute, power, and mechanics.
  • Compare sensors using range, resolution, latency, and failure modes.
  • Select components for a constrained robot task.
Lesson flowHook, model, explanationShow guidance

Inspect the opening phenomenon

Predict what changes, then name the evidence.

Apply in the lab

Name the evidence before reading the answer.

Read only what helps

Then use the lab and recall check.

More when needed

Transcript and resources stay available below.

Course progress

AI & Robotics Foundations · Robot Bodies, Sensors, Actuators, and Compute · Lesson 5

Sensors and Measurement Uncertainty

In progress

Decision challenge

Observe the phenomenon. Then connect the representations.

Use the opening example to make a prediction, identify evidence, and explain which model supports it.

Can a Robot Sensor Ever Tell the Truth?

Predict whether a tight cluster of readings can still be wrong.

A precise reading can still be biased or stale.

Before

Predict whether a tight cluster of readings can still be wrong.

During

Separate noise, bias, resolution, and latency.

After

Name the four parts of decision-ready sensor evidence.

Reference drawerTranscript, source notes, scripts, and package status stay tucked away until you need them.7 files

Lesson reading

live

45 min

Video script

draft

Transcript fallback

available

courses/ai-robotics/modules/02-robot-bodies-sensors-actuators-compute/lessons/02-sensors-and-uncertainty/video-transcript.md

Sensor Evidence Investigation

draft

30 min

Mastery check

live

6 questions / 10 min

Book section:courses/ai-robotics/modules/02-robot-bodies-sensors-actuators-compute/lessons/02-sensors-and-uncertainty/book-section.md
Transcript for accessibility and fallback

# Transcript A robot says the box is exactly one metre away. Should you believe it? A reading is evidence, not ground truth. Noise spreads repeated readings. Bias shifts the whole cluster. Resolution limits meaningful digits. Latency makes a precise reading describe the past. Calibration relates the sensor to a reference under conditions—it does not guarantee every future measurement. A robot needs an estimate, uncertainty, timestamp, and safe fallback. Which is more dangerous: noisy evidence, or precise evidence with hidden bias? Learn to test both in the free EduQuest AI Robotics course. Follow Humanoid Hub.

Reading lab

Core explanation

Connect the lesson's words, diagrams, graphs, evidence, and equations.

Opening challenge: A rover reports that a box is 1.00 m away. What does that number actually prove?

Almost nothing by itself. We need to know what quantity was measured, how the sensor was calibrated, when the reading was captured, the operating conditions, and how much variation or bias could be present.

Sensor evidence chain from physical quantity through calibration and timestamp to an estimate with uncertainty

Mental Model: A Reading Is a Claim With Conditions

NIST describes measurement as a process that produces a value reasonably attributable to a quantity—the measurand. Measurement uncertainty characterizes the dispersion of values that could reasonably be attributed to it. For a robot, useful evidence therefore has at least four parts:

estimate + uncertainty + timestamp + operating conditions

The estimate might be distance, brightness, acceleration, temperature, or wheel rotation. The remaining parts tell the robot whether that estimate is fit for the current decision.

Six Ways Measurements Mislead

EffectWhat it meansEvidence that reveals itPossible response
Random variationRepeated readings spreadrepeated trials, standard deviation, histogramfilter cautiously; preserve variation estimate
BiasReadings are systematically offsetcomparison with a referencecalibrate or correct; investigate cause
ResolutionSensor reports discrete stepssmallest observable incrementavoid claiming finer precision
DriftResponse changes with time or temperaturerepeated reference checksrecalibrate; monitor temperature and age
Latency/stalenessReading describes an earlier statecapture timestamp and arrival timereject stale evidence; slow or stop
Environmental interferenceLighting, reflectivity, vibration, weather, or geometry changes responsecontrolled condition testschange modality, viewpoint, or operating envelope

Accuracy concerns closeness to an accepted reference. Precision concerns the spread of repeated readings. A tight cluster can still be biased. A broad cluster may average near the reference yet remain unreliable for one-shot decisions.

Worked Example: Can the Rover Stop Safely?

A range sensor returns five readings in metres:

0.96, 1.02, 1.00, 0.98, 1.04

Their mean is 1.00 m and the range is 0.08 m. That describes repeatability only under this test. It does not include calibration uncertainty, surface reflectivity, mounting error, or timestamp delay.

Now suppose comparison with a reference repeatedly shows the sensor reads 0.05 m too high. The cluster is precise but biased. A correction may improve the estimate, but the uncertainty of the reference and correction must still be considered.

If the rover moves at 1 m/s and the complete sensing-to-actuation chain is 0.20 s old, the robot travels about 0.20 m while using that evidence. This is why a numerically precise but stale reading can be unsafe.

Calibration Is Not a Magic Certificate

Calibration establishes a relationship between indications and reference values under specified conditions. NIST also warns that later use adds uncertainty from the instrument, method, operator, and environment. Calibration supports traceability; it does not guarantee future performance in every deployment.

Timeliness Is Part of Sensor Quality

ROS 2's sensor-data QoS profile favors timely recent samples over guaranteed delivery of every sample. That trade-off makes sense only when the consumer checks timestamps and defines behavior for missing, delayed, or incompatible data. “Delivered” is not the same as “current.”

Retrieval Pause

Without looking back:

  1. Explain why precision does not prove accuracy.
  2. Name two uncertainty sources that repeated trials alone cannot reveal.
  3. What should a moving robot do when safety-critical range data is stale?

Misconception Checks

“More decimal places mean more certainty.” Display formatting cannot create sensor resolution or reduce uncertainty.

“Averaging removes every error.” Averaging can reduce random variation; it does not automatically remove bias or drift.

“Calibration makes the sensor correct.” Calibration relates indications to references under conditions and with uncertainty.

“Sensor fusion creates truth.” Combining correlated, biased, or stale inputs can produce confident-looking error. Fusion must model provenance and dependence.

A Decision-Ready Sensor Contract

For each measurement stream, record the quantity and units, coordinate frame, timestamp source, expected rate, valid range, resolution, calibration identity, uncertainty model, environmental limits, stale-data threshold, and safe fallback. Test the integrated evidence chain rather than approving a sensor in isolation.

Summary

A robot never receives ground truth directly. It receives indications shaped by physics, calibration, sampling, transport, and the environment. Good robotics makes uncertainty visible, tests both repeatability and bias, preserves timestamps, and changes behavior when evidence is no longer decision-ready.

Sources and Further Learning

Practice labSensor Evidence InvestigationOpen this when you are ready to apply the model, collect evidence, and check your explanation.30 min

Objective

Separate random variation, bias, resolution, and staleness using a simulation-first measurement log.

Materials

Paper or a spreadsheet; no hardware or paid software is required.

Steps

  1. Use readings 98, 101, 99, 102, 100, 99, 101, 100 cm for a reference distance of 100 cm.
  2. Calculate the mean, minimum, maximum, and range. Plot a dot for each reading.
  3. Repeat with 103, 104, 105, 104, 103, 105, 104, 104 cm. Compare spread and offset.
  4. Label which dataset is less biased and which is more precise.
  5. Round both datasets to the nearest 5 cm and explain the information lost through resolution.
  6. Add timestamps at 100 ms intervals. Mark the last three readings stale for a robot whose maximum evidence age is 150 ms.
  7. Create an uncertainty budget containing repeatability, reference uncertainty, mounting, environment, and time delay. Use qualitative low/medium/high values if you have not studied uncertainty propagation.
  8. Define a safe response for out-of-range, stale, missing, and disagreeing measurements.

Expected Result

Submit calculations, two plots, bias/precision classifications, a resolution comparison, stale-data markings, an uncertainty budget, and explicit safe responses. A strong result does not call either dataset “truth.”

Troubleshooting

  • If precision and accuracy seem identical, compare spread separately from offset to the reference.
  • If rounding appears harmless, identify decisions near a threshold.
  • If every fault response is “continue,” define the evidence that proves continued operation is safe.

Reflection Questions

  • Which dataset could look trustworthy while causing the larger systematic error?
  • Which uncertainty components cannot be estimated from repeated readings alone?
  • How should a robot communicate low-confidence evidence to a human operator?

Extension Challenge

Design a two-sensor check without assuming the sensors fail independently. Explain how shared lighting, vibration, power, time, or calibration could correlate their errors.

Accessibility and Offline Path

Use a table instead of a visual plot if needed. All required evidence can be expressed as text. Do not alter safety sensors on real machinery.