There should be a known issues file that lists all the missing features, known bugs, and other things that I plan to improve at some point.
Known Issues
multiple PDDL features are not yet supported (see list of PDDL features supported by plasp)
SAS axiom rules and plasp’s derived predicates (obtained through normalization) are semantically similar, but differently represented in the output format
in compatibility mode, the outdated vars sections within action definitions are handled just like parameters, which is semantically incorrect
several error messages obtained with syntax errors are misleading
There should be a *known issues* file that lists all the missing features, known bugs, and other things that I plan to improve at some point.
### Known Issues
- multiple PDDL features are not yet supported (see list of PDDL features supported by `plasp`)
- SAS axiom rules and `plasp`’s derived predicates (obtained through normalization) are semantically similar, but differently represented in the output format
- the [example encoding](encodings/sequential-incremental.lp) does not support layers of SAS axiom rules
- in compatibility mode, the outdated `vars` sections within action definitions are handled just like `parameters`, which is semantically incorrect
- several error messages obtained with syntax errors are misleading
patrick
added this to the plasp 3.1.0 milestone 2017-11-16 22:15:24 +01:00
patrick
self-assigned this 2017-11-16 22:15:24 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
There should be a known issues file that lists all the missing features, known bugs, and other things that I plan to improve at some point.
Known Issues
plasp)plasp’s derived predicates (obtained through normalization) are semantically similar, but differently represented in the output formatvarssections within action definitions are handled just likeparameters, which is semantically incorrect