Requirements in PDDL are very important. Generally, we can obtain the syntax supported by the current version of PDDL from all requirements of different versions of PDDL. At the same time, adding parameters to the requirements can judge whether the planner used supports a certain syntax (you can also directly start with the requirements mentioned in the paper corresponding to the planner), It can be said that requirements is an indispensable step in learning each version of PDDL.
It is also inevitable that we may encounter a vulnerability that the planner claims to support but in fact only supports syntax parsing...
Here are all the requirements from PDDL to PDDL 3.0 and a brief introduction
Allows you to use the basic add and remove effects specified in strings.
; Add: :effect (walls-built ?s) ; Delete: :effect (not (walls-built ?s))
Allow object typing. Typing is similar to classes and subclasses in object-oriented programming
(:types site material - object bricks cables windows - material )
Allow preferences to be used in problem definitions (soft goals).
Allow constraints in domain definitions (goals that must be met in each state)
(:constraints (and (forall (?l - lorry ?loc - location) (at-most-once (at ?l ? loc))) ))
Allow blocks containing: function representing numeric variables in the field.
(:functions (battery-amount ?r - rover) )
Allow durative action to be used in domain definitions. Continuous action refers to an action with completion duration.
(:durative-action move :parameters (<arguments>) :duration (= ?duration 5) :condition (logical_expression) :effect (logical_expression) )
Inequalities are allowed to represent duration. We can express that an action has a duration range using inequality, rather than expressing that the action has a fixed length of time.
Allows continuous effects on numbers in continuous action. Since the persistence operation takes some time, we can model changes in values as a function of time. In fact, it supports this instability. Linear function is relatively easy for planners, but nonlinear effect is still a research field.
Not is allowed under preconditions. The way some planners imitate actions means that they cannot deal with negative preconditions. This is a serious design flaw for each predicate, which is even more inconvenient because they are an opposite predicate and are true when it is false. That is, Rover charged and Rover not charged are mutually exclusive. When negative preconditions are not supported, we can introduce a second predicate, which represents the negation of the predicate we want to express negative preconditions.
Allow derived predicates in the realm
(:derived (train-usable ?t (and (train-has-guard ?t (train-has-driver ?t ) )
:Timed Initial Literals
Allow Timed Initial Literals when defining issues
(at 10 (train-not-in-use t1))
Allow or objectives and prerequisites
(or (walls-built ?s) (windows-fitted ?s) )
(not (= ?s1 ?s2))
(:requirements :existential-preconditions) (exists (?c - crane) (crane-is-free ?c) )
(forall (?c - crane) (crane-is-free ?c) )
(:requirements :existential-preconditions :universal-preconditions)
when is allowed to express action effects. Basically, if something is true, this effect should also be applied.
(when ;Antecedent (and (has-hot-chocolate ?p ?c) (has-marshmallows ?c)) ;Consequence (and (person-is-happy ?p)) )
Allow action extensions. This allows you to define the effects of variant conditions and actions. In essence, we can define a MOVE action to describe a person's movement, but include different extensions to describe the movement of aircraft, train, car or walking. This has become redundant because we only express multiple actions, such as MOVE-BY-PLANE and MOVE-BY-TRAIN.
Allows the use of foreach action extensions, basically allowing effects to be applied to one or all objects. This requirement implies the existence of requirements, so: action expansions is equivalent to (: Requirements: action expansions: foreach expansions)
Allows you to mark the extensions described in Action Expansions so that you can distinguish the sub actions selected by the scheduler. For example, if we define what an move uses to move simultaneous interpreting modes, we may want to know exactly what patterns the tags use. This requirement implies the existence of requirements, so: Action Expansions is equivalent to (: Requirements: Action Expansions: DAG expansions)
Axioms are allowed. Axioms are essentially predicates implied by other predicates.
See the axiom section in the PDDL 1.2 domain reference
:subgoals through Axioms
In the plan, it is assumed that all unknown values are false. That is, if we don't know the value of the predicate, we think it is false. This is called the "closed world" hypothesis. This requirement changes the planner's assumption of "open world". That is, unknown values are not necessarily wrong. This is rarely supported by modern planners and is usually a sign of plan execution rather than a requirement in the domain.
Please note that not every requirements planner needs to be supported. Different planners have different "strengths" and their supported syntax.
More detailed or specific requirements can be planning.wiki View in.