Execution

Figure 1.18: (a) A planner produces a plan that may be executed by the machine. The planner may either be a machine itself or even a human. (b) Alternatively, the planner may design the entire machine.
\begin{figure}\begin{center}
\begin{tabular}{ccc}
\psfig{file=figs/machenv3.eps,...
...achenv5.eps,width=2.3in} \\
(a) & & (b)
\end{tabular}
\end{center}\end{figure}

A plan is usually executed by a machine. A human could alternatively execute it; however, the case of machine execution is the primary focus of this book. There are two general types of machine execution. The first is depicted in Figure 1.18a, in which the planner produces a plan, which is encoded in some way and given as input to the machine. In this case, the machine is considered programmable and can accept possible plans from a planner before execution. It will generally be assumed that once the plan is given, the machine becomes autonomous and can no longer interact with the planner. Of course, this model could be extended to allow machines to be improved over time by receiving better plans; however, we want a strict notion of autonomy for the discussion of planning in this book. This approach does not prohibit the updating of plans in practice; however, this is not preferred because plans should already be designed to take into account new information during execution.

The second type of machine execution of a plan is depicted in Figure 1.18b. In this case, the plan produced by the planner encodes an entire machine. The plan is a special-purpose machine that is designed to solve the specific tasks given originally to the planner. Under this interpretation, one may be a minimalist and design the simplest machine possible that sufficiently solves the desired tasks. If the plan is encoded as a finite state machine, then it can sometimes be considered as an algorithm in the Turing sense (depending on whether connecting the machine to a tape preserves its operation).

Steven M LaValle 2012-04-20