Add “known issues” file #21

Closed
opened 2017-11-16 22:15:24 +01:00 by patrick · 0 comments
Owner

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 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
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
patrick added the
documentation
task
labels 2017-11-16 22:15:24 +01:00
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

0001-01-01

Dependencies

No dependencies set.

Reference: patrick/plasp#21
No description provided.