patrick
/
plasp
Archived
1
0
Fork 0

Changed format of readme file for STRIPS encodings to Markdown.

This commit is contained in:
Patrick Lühne 2016-11-16 23:27:45 +01:00
parent b1e98bd091
commit c80688b241
Signed by: patrick
GPG Key ID: 05F3611E97A70ABF
1 changed files with 26 additions and 19 deletions

View File

@ -1,31 +1,37 @@
# Incremental STRIPS Planning Encodings
This suite of incremental STRIPS planning encodings implements diverse methods.
The included encoding files provide the following functionalities:
- preprocess.lp: static analysis of potentially relevant actions
+ Parameters: _closure (default value: '3')
* Value '1': forward chaining of effects w.r.t. initial variable values
* Value '2': backward regression of effects w.r.t. goal variable values
* Value '3': both forward chaining and backward regression of effects
* Otherwise: off (simply take all actions as given)
## Encodings
- strips-incremental.lp: sequential and parallel planning encoding variants
+ Parameters: _parallel (default value: '0')
* Value '1': "forall" parallel actions that can be arranged in any sequence
* Value '2': "exists" parallel actions that can be arranged in some sequence
* Otherwise: sequential actions
### [preprocess.lp](preprocess.lp): static analysis of potentially relevant actions
- redundancy.lp: enforcement of 'redundant' actions to constrain parallel plans
+ Remarks:
* Only relevant together with parallel actions
* Encoded constraints seem rather ineffective though
* Heavy space overhead in combination with "exists" parallel actions
* Parameters: `_closure` (default value: `3`)
* Value `1`: forward chaining of effects w.r.t. initial variable values
* Value `2`: backward regression of effects w.r.t. goal variable values
* Value `3`: both forward chaining and backward regression of effects
* Otherwise: off (simply take all actions as given)
- postprocess.lp: plan feasibility checking and conversion to sequential plan
### [strips-incremental.lp](strips-incremental.lp): sequential and parallel planning encoding variants
* Parameters: `_parallel` (default value: `0`)
* Value `1`: “forall” parallel actions that can be arranged in any sequence
* Value `2`: “exists” parallel actions that can be arranged in some sequence
* Otherwise: sequential actions
================================================================================
### [redundancy.lp](redundancy.lp): enforcement of redundant actions to constrain parallel plans
* Remarks:
* Only relevant together with parallel actions
* Encoded constraints seem rather ineffective though
* Heavy space overhead in combination with “exists” parallel actions
Some example invocations (using clingo 5.1.0) are as follows:
### [postprocess.lp](postprocess.lp): plan feasibility checking and conversion to sequential plan
## Usage Examples
Some example invocations (using `clingo` 5.1.0) are as follows:
```bash
plasp ../../instances/PDDL/ipc-2000-elevator-m10-strips/domain.pddl ../../instances/PDDL/ipc-2000-elevator-m10-strips/problem-04-00.pddl | clingo - preprocess.lp strips-incremental.lp
plasp ../../instances/PDDL/ipc-2000-elevator-m10-strips/domain.pddl ../../instances/PDDL/ipc-2000-elevator-m10-strips/problem-04-00.pddl | clingo - preprocess.lp strips-incremental.lp -c _closure=0
@ -47,3 +53,4 @@ plasp ../../instances/PDDL/ipc-2000-elevator-m10-strips/domain.pddl ../../instan
plasp ../../instances/PDDL/ipc-2000-elevator-m10-strips/domain.pddl ../../instances/PDDL/ipc-2000-elevator-m10-strips/problem-04-00.pddl | clingo - preprocess.lp strips-incremental.lp --outf=1 -c _parallel=1 | grep -A1 -e "ANSWER" | tail -n1 | clingo - postprocess.lp <(plasp ../../instances/PDDL/ipc-2000-elevator-m10-strips/domain.pddl ../../instances/PDDL/ipc-2000-elevator-m10-strips/problem-04-00.pddl)
plasp ../../instances/PDDL/ipc-2000-elevator-m10-strips/domain.pddl ../../instances/PDDL/ipc-2000-elevator-m10-strips/problem-04-00.pddl | clingo - preprocess.lp strips-incremental.lp --outf=1 -c _parallel=2 | grep -A1 -e "ANSWER" | tail -n1 | clingo - postprocess.lp <(plasp ../../instances/PDDL/ipc-2000-elevator-m10-strips/domain.pddl ../../instances/PDDL/ipc-2000-elevator-m10-strips/problem-04-00.pddl)
```