← Back to the chapter · Previous detail · Next detail →

Technical detail · Mobile Sensing: Features and Deployment

Keep the deployment contract together

The deployment contract should preserve sample rate, timestamp tolerance, window length, overlap, placement assumption, feature code, classifier version, threshold, and fallback behavior together. If the operating system later batches sensors to save power, the same feature extractor may receive irregular intervals and stale windows. If a quantized model replaces a larger classifier, class boundaries and confidence calibration need a replay check before release. The review should treat those changes as evidence changes, not just implementation changes. A useful release record stores replay results by class and placement, so a later regression can be traced to sensor timing, feature drift, threshold choice, or model conversion instead of being described as a vague accuracy drop. Include failed windows too, because their pattern often reveals the actual deployment boundary.

← Back to the chapter · Previous detail · Next detail →