Resolution, sensitivity, dynamic range

"They asked me to detect a whisper and a thunderclap with the same ear, and to tell apart two whispers a hair's breadth apart. I asked which one mattered more, and they said yes."

An Overspecified AI Agent

Section 2.1 established the measurement model \(x = h(s) + \eta\): a hidden state \(s\) passes through the sensor response \(h(\cdot)\) and is digitized into a reading \(x\). This section characterizes the properties of that pipeline that cap its information content, deliberately setting aside the statistics of the noise term \(\eta\) (the subject of Section 2.3) and the failure of \(h(\cdot)\) at its extremes (Section 2.4). We assume only basic calculus and the notion of the transfer function from the previous section. If quantization and sampling feel unfamiliar, they are treated in depth in Chapter 3.

Resolution: the smallest distinguishable change

What. Resolution is the smallest increment of the measured quantity that produces a detectable, repeatable change at the output. Why it matters. It is a hard floor on discrimination: if two states differ by less than one resolution step, the sensor reports the same value for both, and no filter, no network, no amount of averaging over those two identical readings can separate them. How it arises. Two mechanisms set it. The first is quantization. An analog-to-digital converter with \(N\) bits carves its full-scale span \(V_\text{FS}\) into \(2^N\) levels, so the least-significant-bit step, the smallest number it can represent, is

$$\Delta = \frac{V_\text{FS}}{2^{N}}.$$

A 12-bit converter spanning \(\pm 2\,\text{g}\) on an accelerometer resolves \(4\,\text{g} / 4096 \approx 0.98\,\text{mg}\) per step. The second mechanism is the analog noise floor: even before digitization, thermal and electronic noise blur the output, so a converter with more bits than the analog stage warrants simply digitizes noise. The honest figure is the effective number of bits (ENOB), which discounts the nominal bit count by the measured noise. Resolution is also spatial and temporal, not only in amplitude: a thermal camera's resolution is its pixel pitch on the scene, and a heart-rate sensor's temporal resolution is set by its sampling interval.

Sensitivity: how hard the needle moves

What. Sensitivity is the slope of the transfer function: the change in output per unit change in the input, \(\;S = \mathrm{d}x / \mathrm{d}s\). For a linear sensor it is a single constant (a load cell might give \(2\,\text{mV/V}\) at full load; a photodiode's responsivity might be \(0.6\,\text{A/W}\)). Why it matters. Sensitivity governs how a fixed amount of input maps onto the converter's steps, and so it interacts directly with resolution. A high-sensitivity sensor spreads a small physical change across many ADC codes, making that change easy to see; a low-sensitivity sensor compresses the same change into a fraction of one code, where it vanishes. How to reason about it. The catch is that sensitivity and range pull in opposite directions. Cranking gain to boost sensitivity moves faint signals up into many codes, but it also drives strong signals off the top of the scale into saturation. This is why sensitivity is a design knob, not a virtue to maximize blindly.

A common confusion is to treat "sensitive" and "high-resolution" as the same claim. They are linked but distinct. Sensitivity is a property of the analog transduction (slope), resolution is a property of the whole chain including the converter (step size). You can raise effective resolution by raising sensitivity until you hit noise or saturation, at which point more gain buys nothing. The quantity that actually limits detection of faint signals is the ratio of sensitivity to noise, which is where Section 2.3 on signal-to-noise ratio takes over.

Dynamic range: from the faintest to the loudest

What. Dynamic range is the ratio of the largest signal a sensor can measure (its full scale, just below saturation) to the smallest it can resolve (its noise floor or one quantization step, whichever is larger). Because that ratio spans orders of magnitude, it is quoted in decibels, and for a converter it maps neatly onto bit depth:

$$\text{DR}_\text{dB} = 20 \log_{10}\!\left(\frac{x_\text{max}}{x_\text{min}}\right) \approx 6.02\,N + 1.76 \;\text{ for an ideal } N\text{-bit converter}.$$

Why it matters. The physical world routinely presents signals across a huge range within one deployment. A microphone in a car must handle a quiet cabin and a slamming door; an automotive lidar return from a black tire at range and a retroreflective sign differ by many orders of magnitude; an IMU on a drone sees both gentle hover drift and the shock of a hard landing. If the required span exceeds the sensor's dynamic range, you are forced to choose which end to sacrifice, and something important gets clipped or lost in the noise. How to extend it. When one fixed setting cannot cover the span, systems use auto-ranging (switching gain on the fly, as a camera does with exposure), companding (compressing large signals nonlinearly), or multiple parallel channels. Each buys range at the cost of complexity, latency, or a discontinuity the downstream model must be told about. Note that the floor is set by noise (Section 2.3) and the ceiling by saturation (Section 2.4); dynamic range is the clean summary of the two you own from this section.

import numpy as np

def adc_specs(v_full_scale, n_bits, noise_rms):
    step = v_full_scale / (2 ** n_bits)          # quantization resolution (LSB)
    enob = n_bits - np.log2(max(noise_rms / step, 1.0))  # bits lost to noise
    dr_db = 20 * np.log10(v_full_scale / max(noise_rms, step))
    return step, enob, dr_db

for bits in (8, 12, 16):
    step, enob, dr = adc_specs(v_full_scale=4.0, n_bits=bits, noise_rms=3e-3)
    print(f"{bits:2d}-bit: step={step*1e3:7.3f} mV  ENOB={enob:4.1f}  DR={dr:5.1f} dB")

The snippet above makes the central trade concrete. Holding the analog noise fixed at 3 mV, the 8-bit and 12-bit converters gain real resolution, but the 16-bit part reports far more nominal precision than its ENOB, because the noise floor, not the bit count, sets the true smallest distinguishable step. This is why "how many bits" is the wrong first question; "what is the ratio of the loudest signal I must not clip to the faintest I must still see" is the right one.

from scipy.signal import periodogram
f, pxx = periodogram(samples, fs=fs, window="blackmanharris")
# locate fundamental bin, sum the rest as noise+distortion, then:
# ENOB = (SINAD_dB - 1.76) / 6.02

Matching the three to the task

The three specifications are not chosen in isolation; they are matched to what the application actually needs to distinguish, and against each other. Start from the decision the system must make, translate it into a required smallest distinguishable change (this sets resolution and, through the noise floor, the needed sensitivity) and a required span of operating conditions (this sets dynamic range). Only then pick hardware. A gesture classifier on an inertial sensor needs modest resolution but wide range to survive impacts; a tremor-monitoring clinical device needs the opposite, fine resolution over a narrow band. Getting this mapping right is upstream of every model you will train, and it feeds directly into how you reason about what the resulting estimates can and cannot claim, which is the uncertainty machinery of Chapter 4.

What's Next

In Section 2.3, we open up the noise term \(\eta\) we kept sealed here. Resolution and dynamic range both bottomed out on a "noise floor" we treated as a given; the next section names the physical sources of that floor (thermal, shot, flicker, quantization), shows how they combine, and turns the vague phrase "signal-to-noise ratio" into a quantity you can compute, budget, and improve.