Equation 3 · From Origins to Frontier: A History of Robotics and Embodied AI
What does this equation mean?
Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.
This equation gives an approximation: it relates the quantities while allowing an approximation. Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.
Read it piece by piece
Symbol P_finish
inish is a part of this expression. Its role is fixed by the surrounding article and by the operations shown in the formula.
Symbol q
q is a part of this expression. Its role is fixed by the surrounding article and by the operations shown in the formula.
Symbol L
L is a part of this expression. Its role is fixed by the surrounding article and by the operations shown in the formula.
subscript
The lower label selects a particular version, component, or indexed member of the quantity. For example, x₀ and xₜ can be values at different positions.
superscript
A raised number can be a power. When it is a label or bound, it selects a case or the upper limit of a sum; the formula’s structure distinguishes these uses.
See an illustrated explanation →How to interpret it
Its accuracy depends on the assumptions and range of use described in the article.
What the article says around this equation
The arithmetic behind that result is worth making explicit, because it explains why the next eighteen months mattered more than the raw distance suggests. If a course of length L miles must be driven without a mission-ending error, and a vehicle’s probability of such an error is q per mile and roughly independent from one mile to the next, the probability of finishing the course is approximately . Over a 142-mile course, even a per-mile reliability of 99 percent yields a finishing probability under 25 percent, and the 2004 fleet did not come close to that bar. This is illustrative arithmetic rather than a number drawn from any cited study, but it frames what changed by…
Read the full surrounding passage
The arithmetic behind that result is worth making explicit, because it explains why the next eighteen months mattered more than the raw distance suggests. If a course of length L miles must be driven without a mission-ending error, and a vehicle’s probability of such an error is q per mile and roughly independent from one mile to the next, the probability of finishing the course is approximately . Over a 142-mile course, even a per-mile reliability of 99 percent yields a finishing probability under 25 percent, and the 2004 fleet did not come close to that bar. This is illustrative arithmetic rather than a number drawn from any cited study, but it frames what changed by October 2005: Stanford’s Stanley, built by a team led by Sebastian Thrun and documented in a paper with 29 co-authors, completed a desert course of comparable length in 6 hours 53 minutes, using a probabilistic software stack — machine-learned terrain classification, laser- and vision-based obstacle detection, and adaptive speed control — rather than a faster version of the 2004 approach [ 9 ] . The qualitative change between the two years was not speed. It was a roughly order-of-magnitude reduction in the rate of the errors that had stranded the 2004 fleet in the desert.
Sources cited in the surrounding passage
These citations give research context. Read each source to check which claims it supports.
Return to From Origins to Frontier: A History of Robotics and Embodied AI