Commit 506e6e25 authored by Markus Klinik's avatar Markus Klinik
Browse files

wording

parent 7af4f2ec
......@@ -8,7 +8,7 @@ The state of the art in automated planning is called \emph{classical planning}.
In classical planning, the state of the world is a set of nullary predicates called \emph{fluids}.
An action consists of a precondition and an effect.
The precondition is a set of fluids that must be included in the current state in order for an action to be executable.
The effect of an action is two sets of fluids, one that is added to the state and one that is deleted.
The effect of an action consists of two sets of fluids, one that is added to the state and one that is deleted.
When the action is executed, the state is modified according to the action's effect.
A concise definition of classical planning is given by \citet{MuiseBM2016}.
......@@ -20,7 +20,8 @@ It is supported by virtually every planner currently in existence.
For C2, planning is only one part in the decision support process.
The result of planning is fed as input to scheduling.
In order to give the scheduler leeway to find a good schedule, the plan should not be a list of actions, to be executed in exactly this order, but a partially ordered set of actions.
In order to give the scheduler leeway to find a good schedule, the plan should not be a list of actions, to be executed in exactly this order.
Instead, it should be a partially ordered set of actions.
All actions that are not explicitly constrained by the partial ordering should be executable in any order, and even concurrently.
Most classical planners have as output a list of actions that are to be executed in exactly this order.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment