patrick
/
plasp
Archived
1
0
Fork 0
This repository has been archived on 2023-07-19. You can view files and clone it, but cannot push or open issues or pull requests.
plasp/doc/output-format.md

76 lines
2.2 KiB
Markdown
Raw Normal View History

# Output Format
`plasp` 3 translates SAS and PDDL files into the same ASP fact format.
2016-08-13 17:39:39 +02:00
`plasp` structures the translated ASP facts into the multiple sections, which are explained in the following.
## Feature Requirements
2016-08-13 17:39:39 +02:00
Declares advanced features required by the input planning problem, such as conditional effects and axiom rules.
2016-08-13 17:42:02 +02:00
Feature requirements may be used in meta encodings to warn about unsupported features.
2016-08-13 17:39:39 +02:00
### Syntax
2016-08-13 17:39:39 +02:00
syntax | description
-------|------------
`requiresFeature(<feature name>).` | declares the feature `<feature name>` to be required by the input problem
2016-08-13 17:39:39 +02:00
Currently, feature requirements are only recognized with SAS problems.
`plasp` supports the following feature requirements:
2016-08-13 17:39:39 +02:00
SAS feature | description
------------|------------
`actionCosts` | actions have associated costs
2016-08-13 17:42:02 +02:00
`axiomRules` | immediate actions are used, which are executed as soon as the preconditions are satisfied
2016-08-13 17:39:39 +02:00
`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).
```
2016-08-13 18:05:58 +02:00
## Types (PDDL Only)
Specifies all object types used by the PDDL problem (only if typing is enabled).
### Syntax
syntax | description
-------|------------
`type(type(<type name>)).` | declares the type `type(<type name>)`
`has(<object>, type(<type name>)).` | declares `<object>` to be of type `type(<type name>)`
### Example
The following declares the type `type(block)` for later usage by the problem:
```prolog
% types
type(type(block)).
```
[Constants](#constants) may have associated types (here, `constant(a)`):
```prolog
constant(constant(a)).
has(constant(a), type(block)).
```
If there is typing information, [variables](#variables) are derived only for the allowed types (here, `variable(clear(X))` with `type(block)`):
```prolog
variable(variable(clear(X))) :- has(X, type(block)).
```
Similarly, [actions](#actions) are derived in a type-safe way (here, `action(stack(X, Y))` is only applicable to arguments of `type(block)`):
```prolog
action(action(stack(X, Y))) :- has(X, type(block)), has(Y, type(block)).
```