Contributors: adamgreen, Adam Green, Jan Dolejsi,
PDDL 3.0 introduced soft goals to planning. As planning has grown to handle larger more complex problem, the way we express goals has had to change. In previous editions a goal was unavoidable. It had to be met in order for a a plan to be considered valid.
With the introduction of preferences (soft goals), we are now able to express a desireable, but inconsequential goal. A goal which we would like to be satisfied but if it is not, then that is acceptable.
For each soft goal we express, we include a cost for not meeting it. This cost essentially indicates how the plan quality is affected when such goal is not met.
PDDL 3.0 also introduced constraints, a form of strong goal, which essentially can use the same keywords as used for preferences, but instead must be met for the plan to be considered valid.
This allows us to express things such as facts that must become true after another, or facts which must always be true. See the keywords included in the Constraints and Preferences sections below.
- PDDL - The Planning Domain Definition Language, [Ghallab, M. Howe, A. Knoblock, C. McDermott, D. Ram, A. Veloso, M. Weld, D. Wilkins, D.]
- PDDL2.1: An Extension to PDDL for Expressing Temporal Planning Domains, [Fox, M. Long, D.]
- PDDL2.2: The Language for the Classical Part of the 4th International Planning Competition [Edelkamp, S. Hoffmann, J.]
- Plan Constraints and Preferences in PDDL 3 [Gerevini, A. Long, D.]
- BNF Description of PDDL 3.0 [Gerevini, A. Long, D.]
- PDDL Examples
- OPTIC - Optimising Preferences and Time Dependent Costs