From 18ac959970c78e3be73346fbdab71da8e0d70af5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Patrick=20L=C3=BChne?= Date: Sat, 13 Aug 2016 17:52:27 +0200 Subject: [PATCH] Restructured documentation of feature requirements and added an example. --- doc/output-format.md | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/doc/output-format.md b/doc/output-format.md index b42a7b7..fe176a3 100644 --- a/doc/output-format.md +++ b/doc/output-format.md @@ -2,24 +2,35 @@ `plasp` 3 translates SAS and PDDL files into the same ASP fact format. -## Syntax and Semantics - `plasp` structures the translated ASP facts into the multiple sections, which are explained in the following. -### Feature Requirements +## Feature Requirements Declares advanced features required by the input planning problem, such as conditional effects and axiom rules. Feature requirements may be used in meta encodings to warn about unsupported features. +### Syntax + syntax | description -------|------------ -`requiresFeature().` | declares the feature `` to be required by the input problem +`requiresFeature().` | declares the feature `` to be required by the input problem Currently, feature requirements are only recognized with SAS problems. +`plasp` supports the following feature requirements: SAS feature | description ------------|------------ `actionCosts` | actions have associated costs `axiomRules` | immediate actions are used, which are executed as soon as the preconditions are satisfied `conditionalEffects` | some effects of an action may have additional conditions + +### Example + +The following specifies that the input problem has the two requirements `actionCosts` and `conditionalEffects`. + +```prolog +% requirements +requiresFeature(actionCosts). +requiresFeature(conditionalEffects). +```