Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Partial start state for reachability query #137

Open
Mati-AAU opened this issue Dec 14, 2022 · 0 comments
Open

Partial start state for reachability query #137

Mati-AAU opened this issue Dec 14, 2022 · 0 comments

Comments

@Mati-AAU
Copy link
Contributor

Mati-AAU commented Dec 14, 2022

The reachability query currently supports partial end states, but not partial start states.

Partial states are states where atleast one location is marked as being any location.
This means that a partial location represents many states in a transition system.

This will require changes in the grammar, the parser, and the algorithm itself.

Will probably work similarly to partial end states in the grammar and parser, however will be implemented differently to partial end states in the algorithm itself.

I think the easiest way to implement it, is to in the find_path or reachability_search_algorithm function, to iterate through all states that the start state represents, and add each of them to the frontier, instead of only adding one state to the frontier, which should be correct and also be performant.

Examples of queries with partial start states where it should return reachable.
Machine -> [_](y>6); [_](y<2)
Machine || Researcher -> [_, _](x>6); [_, _](x<2)
Machine || Researcher -> [_, _](y>6); [L5, _](y<2)

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

No branches or pull requests

1 participant