Visitar URL original
refinement relation between `nondetE` trees · Issue #42 · DeepSpec/InteractionTrees · GitHub
Skip to content

refinement relation between nondetE trees #42

Open

Description

@aa755

Has there been work on defining a refinement relation between trees that have the nondetE effect, saying that t1 refines t2 iff for every choice made for the nondetE actions in t1, there exists a choice for nondetE actions in t2 such that the rest of the two trees line up?

Activity

  1. gmalecha commented on Jan 11, 2019

    @gmalecha
    Collaborator

    We wrote some of this out, didn't we?

  2. Lysxia commented on Jan 12, 2019

    @Lysxia
    Collaborator

    There is something like that in our DeepWeb experiment but it's unused. In the VST proof we use trace inclusion, which is a coarser relation, but I'm pretty sure the lemmas we actually proved are all compatible with this tree refinement relation, which is a kind of simulation.

  3. added
    itreesParticular to theory and implementation of itrees
    on Mar 27, 2019
  4. jeehoonkang commented on Apr 8, 2019

    @jeehoonkang
    Contributor

    I'd also like to use interaction trees for proving behavior refinement (not equivalence) and wonder if supporting simulation (not bisimulation) is on the roadmap. If not, people in my group are willing to contribute to it.

  5. Lysxia commented on Apr 8, 2019

    @Lysxia
    Collaborator
  6. jeehoonkang commented on Apr 9, 2019

    @jeehoonkang
    Contributor

    @Lysxia Thank you for your detailed answer. Your second and third bullet explains ideas on solutions, but I don't quite understand the problem. May I ask if why it would be difficult to support interaction tree refinement?

  7. Lysxia commented on Apr 10, 2019

    @Lysxia
    Collaborator

    Good question. I think the main problem is a problem of generality, so I may be getting carried away. Simulation is one example out of many other relations we may want to support, and we might even want to be able to combine some of them. To fit them all under a common framework is why I'm looking at those solutions.

    In this light, a different way to approach this issue is to look at some concrete definition of simulation and decide that it is good enough for most purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestitreesParticular to theory and implementation of itrees

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions