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

Bisimulation: add a note about requirements of bisimulation #785

Draft
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

fangyi-zhou
Copy link
Contributor

Two simulations only form a bisimulation when the underlying relation are inverses of each other:
https://cs.stackexchange.com/questions/541/when-are-two-simulations-not-a-bisimulation

This commits adds clarification over the matter, by emphasising the inverse requirement.

Signed-off-by: Fangyi Zhou [email protected]

@wadler
Copy link
Member

wadler commented Nov 11, 2022

Thank you. You are correct, the current discussion is too compact. But I think the sudden reference to ~⁻¹ may be confusing to students. I'll have a think about the best way to explain.

@fangyi-zhou
Copy link
Contributor Author

Thanks for the reply. I agree that the current way to present this subtlety is probably not the best.
Ideally, we first introduce the concept/definition of bisimulation:

Simulation: For every M, M†, and N: If M ~ M† and M —→ N then M† —↠ N† and N ~ N† for some N†.
Bisimulation: For every M, M†, and N: Suppose M ~ M†, if (1) M —→ N then M† —↠ N† and N ~ N† for some N†, and (2) if M† —→ N† then M —↠ N and N ~ N† for some N

then the difference between 2-simulation and bisimulation?

@wenkokke wenkokke force-pushed the bisimulation-reword branch from 6ee5377 to 4a046aa Compare February 7, 2023 13:55
Two simulations only form a bisimulation when the underlying relation
are inverses of each other:
https://cs.stackexchange.com/questions/541/when-are-two-simulations-not-a-bisimulation

This commits adds clarification over the matter, by emphasising the
inverse requirement.

Signed-off-by: Fangyi Zhou <[email protected]>
@wenkokke wenkokke force-pushed the bisimulation-reword branch from 4a046aa to 2f5f133 Compare February 10, 2023 18:28
@wenkokke wenkokke marked this pull request as draft February 25, 2023 00:15
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.

2 participants