Common offset in RC timing

ID: common-offset-in-rc-timing

A common offset in RC timing cancels only when every level used in the crossing model shares the same additive change. For high level , threshold , and initial baseline , assume and fixed time constant . The crossing time is
Adding to all three levels leaves both differences unchanged, so the invariance in the header is exact. It describes a shared readout zero, or an equivalently translated step with a translated initial condition, rather than every possible physical offset experiment.
The three sensitivities make the cancellation visible locally:
A common random offset has covariance matrix for these three inputs and contributes zero to the propagated timing variance. NIST's primary law retains exactly such covariance terms; setting them to zero would represent another measurement model.[ref]
For an original nonzero-baseline example, take , , and . The crossing is about . Adding to all three levels leaves it exactly unchanged. Adding the same offset only to and while keeping the baseline fixed instead increases it by about . The two-level sensitivity is , predicting to first order.
A calibration test must state whether the initial capacitor output, electronic comparator reference, input level and readout share the offset. Independent threshold errors, uncertainty of the time constant, and baseline memory remain even when this one common component cancels. The full distinction is developed in correlated threshold and amplitude errors in RC timing; a common gain is a separate invariance treated in ratiometric cancellation of RC timing gain errors.

New to topics? Read the docs here!