Skip to content

Add verficiation feature for Golog programs#187

Draft
snoato wants to merge 7 commits intomainfrom
snoato/feature/golog-verification
Draft

Add verficiation feature for Golog programs#187
snoato wants to merge 7 commits intomainfrom
snoato/feature/golog-verification

Conversation

@snoato
Copy link
Collaborator

@snoato snoato commented Mar 6, 2023

No description provided.

snoato added 4 commits March 9, 2023 16:33
The idea of verification for Golog programs is that if the tree search
for a given program + MTL specification sans controller actions (i.e.
every action is an environment action), leads to the root node being
labelled as top, then no execution of the Golog program violates the
given specification, i.e. the program is safe against the specification.
On the other hand if the resulting tree labels the root node as bottom,
then there is at least one unsafe execution path of the program. In this
case, finding the path gives a counter-example against the MTL spec. A
simple path traversal on a fully built search tree towards a top or
bottom labelled leaf node is to be implemented in these files, to
enable gocos to do Golog program verification.
In verification mode, we want to generate a possibly minimal counter
example of an execution trace of a golog program violating the given
constraints. To achieve this, we traverse the search tree until we
reach a bottom labelled node.
@snoato snoato force-pushed the snoato/feature/golog-verification branch from 0c89e92 to e33ee0a Compare March 9, 2023 15:33
snoato added 3 commits April 5, 2023 15:07
In order to better understand the generated counter example, a
program execution trace is extracted from the search tree and printed
with concrete candidate clock valuations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant