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

Obtaning proof of non-simulation #56

Open
aubertc opened this issue Feb 15, 2023 · 3 comments
Open

Obtaning proof of non-simulation #56

aubertc opened this issue Feb 15, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@aubertc
Copy link
Member

aubertc commented Feb 15, 2023

This is a follow-up of the discussion started at #33.

Is there an easy way to output the strategy the program found to assert that two processes were not in capacity of simulating each other?

For instance, consider

p = a.((b.c) + (b.d))
q = a.b.(c+d)

Then, p cannot simulate q, because q can "trick" p by doing a, then b (and at this moment p needs to make a choice), and then q can pick c or d, while p is forced to follow the choice it made previously.

Is there an easy way to compute, and then picture / present this?

@aubertc aubertc added the enhancement New feature or request label Apr 26, 2023
@peterbro1
Copy link
Collaborator

Closed as complete in latest release, using --equivalence flag

@peterbro1
Copy link
Collaborator

[0] a0.(b1.c2+b3.d4) => Parsed Successfully.
[1] a0.b1.(c2+d3) => Parsed Successfully.

Simulations and Bisimulations:

a0.(b1.c2+b3.d4) ≲ a0.b1.(c2+d3)

Process finished with exit code 0

@aubertc
Copy link
Member Author

aubertc commented Apr 27, 2023

It's something slightly more subtle than that: can we output any information when there is no simulation?

For instance, as of now we have:

java -jar target/IRDC-4.1.1.1-jar-with-dependencies.jar --equivalence "a.((b.c)+(b.d)), a.b.(c+d)"
[0] a.(b.c+b.d) => Parsed Successfully.
[1] a.b.(c+d) => Parsed Successfully.


Simulations and Bisimulations: 
 ------------
a.(b.c+b.d) ≲ a.b.(c+d)

This improvement is asking the program to output something explaning why a simulation the other way around does not work (a strategy to trick one process). Something along the lines of:

Both processes can do a then b, but then the first must do either c or d, while the other one can do both.

This is a complicated issue :-)

@aubertc aubertc reopened this Apr 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants