Constraint redundancy in baseline-noise minimization occurs when some signal-preservation or baseline-rejection conditions are linear combinations of others. In minimum-noise weights under baseline moment constraints, the estimator weights satisfy . A necessary and sufficient feasibility condition is
Indeed, multiplying the constraints by gives necessity. Sufficiency follows because the range of is the orthogonal complement of the kernel of . Redundant conditions are harmless only when their required responses obey the same dependencies.
For an original three-sample example, let the pulse template be and the constant baseline . The columns contain a duplicated baseline condition. The required response is feasible and gives the same minimum-noise weights as the two independent columns alone. With independent sample variance , its variance remains ; writing the constant condition twice adds no information.
By contrast, requiring responses would demand both and . The dependency has , exposing the inconsistency.
With positive-definite error covariance and feasible constraints, put . A redundant-column version of the optimum is
where is the Moore-Penrose inverse. Feasibility ensures . Without the null-space feasibility test for baseline-estimator constraints, this formula can silently return approximate responses instead of the requested exact cancellations. Variance still uses the full covariance quadratic form.[ref]
NIST's before/after pulse baselines motivate such cancellation constraints experimentally.[ref] A singular value decomposition can diagnose numerical dependence, but a small singular value caused by time units or poor scaling is not automatically permission to discard a physical drift-rejection requirement.
A numerical feasibility residual for baseline constraints measures how closely computed pulse-estimator weights satisfy their requested responses. For , evaluate
This is not the same diagnostic as the projected unattainable response in null-space feasibility test for baseline-estimator constraints. That test asks whether a solution exists at the chosen matrix rank; the residual checks the weights actually returned.
Small numerical components need physical scaling. If the measurement model is , an estimator intended to preserve the signal and reject the backgrounds instead has bias
Thus an unweighted Euclidean residual norm is not a universal error bound. Coefficient magnitudes and the units of each constraint matter.
For an original example, suppose the constant-background residual is and the linear-time residual is . A background offset contributes through the first residual. A drift rate also contributes through the second. The much smaller raw numerical value is not a much smaller physical leakage. Expressing time in microseconds changes to without changing that leakage.
A response-normalized tolerance for baseline-feasibility residuals can specify allowed response errors in matching units and check . When coefficient bounds , are justified, the corresponding bias bound is . A noise-minimizing estimator still needs a separate variance calculation from the actual covariance.[ref]
NIST's before/after pulse baselines provide the physical setting for rejecting background and drift.[ref] Report the chosen constraint scaling and tolerated leakage. A small solver residual alone establishes neither low variance nor negligible bias for every possible background.