ASP planning tools for PDDL (local mirror of for development purposes)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Patrick Lühne af325e3991
Version bump after release 3.1.1.
5 years ago
app Version bump after release 3.1.1. 5 years ago
doc Added PDDL 3.1 feature support documentation. 5 years ago
encodings Excluding derived variables from inertia. 5 years ago
include/plasp Replacing user-defined variable names. 5 years ago
instances Moved IPC 2000 Elevator example instances to instance directory. 6 years ago
lib Updated cxxopts to 2.0.0. 5 years ago
src Replacing user-defined variable names. 5 years ago
tests Added tests for derived predicate numbering. 5 years ago
.gitattributes Hiding example instances from Linguist. 6 years ago
.gitignore Initial commit. 7 years ago
.gitmodules Updated Catch to 2.0.1. 5 years ago
.travis.yml Removed Boost packages from Travis configuration. 5 years ago Version bump after release 3.1.1. 5 years ago
CMakeLists.txt Made option group parsing more uniform. 5 years ago Updated documentation to new output format. 5 years ago Changed license to Markdown format. 7 years ago Added PDDL 3.1 feature support documentation. 5 years ago

plasp GitHub Release Build Status Build Status

ASP planning tools for PDDL


plasp is a tool collection for planning in answer set programming. plasp 3 supports the input languages PDDL 3.1 (except for advanced features such as durative actions, numerical fluents, and preferences) and SAS (full support of SAS 3), which is used by Fast Downward.

The most notable tool provided by plasp is plasp translate, which translates PDDL descriptions to ASP facts.

Translating PDDL to ASP Facts

PDDL instances are translated to ASP facts as follows:

plasp translate domain.pddl problem.pddl

Alternatively, PDDL instances may first be translated to SAS, the output format of Fast Downward.

./ --translate --build=release64 domain.pddl problem.pddl

This creates a file called, which may now be translated by plasp as well.

plasp translate

Solving the Translated Instance

The translated instance can finally be solved with clingo and a meta encoding, for instance, sequential-horizon.lp:

plasp translate domain.pddl problem.pddl > instance.lp
clingo encodings/sequential-horizon.lp -c horizon=10 instance.lp

Translator Output Format

plasp translate provides a uniform output format for SAS and PDDL input problems. See output format for more details.

If you want to write your own meta encoding for plasp translate’s output, this simple example encoding gets you started.

Provided Tools

plasp <command> [<option>...] [<input file>...]

Aside from translating PDDL to ASP facts, plasp provides the following commands:

command description
translate Translate PDDL and SAS to ASP facts
normalize Normalize PDDL to plasp’s custom PDDL format
check-syntax Check the syntax of PDDL specifications
beautify Cleanly format PDDL specifications
help Display help message
version Display version information

plasp help shows a list of all commands provided by plasp. To list all available options of a command, call plasp <command> --help or plasp help <command>.

plasp automatically detects the language (PDDL or SAS) of the input descriptions.


plasp is built with CMake and a C++ compiler. See building for more details.

PDDL Feature Support

plasp supports a subset of PDDL 3.1. See PDDL feature support for a list of supported and unsupported PDDL 3.1 features.


Earlier Versions

  • René Knaebel
  • Murat Knecht