Multi-sample consistency of distance-query intervals

ID: multi-sample-consistency-of-distance-query-intervals

Multi-sample consistency of distance-query intervals asks whether every bounded distance reading can belong to one nonnegative clearance function with the claimed Lipschitz constant. The same motion history must explain all samples. Checking each adjacent pair in isolation can select a different intermediate distance for each check and miss a contradiction.
Let strictly increasing times have nonempty intervals , with , and let bound clearance change per unit time. Necessary and sufficient conditions are
Necessity follows by comparing any feasible distances using Lipschitz continuity. For sufficiency, construct
Each envelope has Lipschitz constant at most . The pairwise conditions and the triangle inequality imply everywhere. At each sample time, , so itself is an admissible nonnegative clearance history. This proves existence, not that this constructed history is the robot's actual history.
The intervals are exact feasible projections at sample times. Both bounding functions are feasible and convex combinations of them remain feasible, so every intermediate value at one fixed time is attainable. The associated multi-sample clearance envelope also gives between-sample lower bounds for a clearance certificate with bounded distance-query error.
For an original counterexample to adjacent-only testing, let successive times differ by one second, take , and use
The first adjacent pair can use middle distance , and the second can use middle distance ; each pair is compatible. Yet the endpoints require a change in two seconds, exceeding the allowed . No common history exists.
An equivalent linear-time feasibility test propagates a reachable interval. Start and recursively set
Stop if an interval becomes empty. In the example, and the next propagated upper bound is , so is empty. Retaining the tightened interval is the key difference from independent adjacent-pair checks. If all intervals remain nonempty, select a final value and work backward through the reachable intervals; piecewise linear interpolation yields a feasible history.
Incompatibility diagnoses inconsistent readings or assumptions, not a demonstrated collision. Compatibility proves only the existence of a scalar clearance history; it does not prove that some rigid robot trajectory realizes that history or that the true clearance stays positive. Continuous collision avoidance remains a constraint along the physical path, as in the primary motion-planning formulation.[ref] A proposed implementation tests synthetic histories with known bounds, deliberately inconsistent triples and timestamp errors, keeping model inconsistency separate from insufficient clearance.

New to topics? Read the docs here!