Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E escet
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 91
    • Issues 91
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 7
    • Merge requests 7
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse Projects
  • Eclipse ESCET (Supervisory Control Engineering Toolkit)
  • escet
  • Issues
  • #147

Closed
Open
Created Jul 16, 2021 by Ferdie Reijnen@freijnenDeveloper

Reconsider CIF to CIF remove requirements

This CIF to CIF transformation removes requirement invariants and requirement automata from a specification. It is used by databased synthesis to post-process the resulting specification.

For requirement automata, everything declared inside them is removed, except for kindless, plant, and supervisor invariants. Those are moved to the parent component. If from the outside a declaration inside the automaton is referenced, the transformation fails. However, the following question remains:

What about removing initialization predicates, marker predicates in requirement automata, that really restrict or apply to the plant? Probably somewhat difficult to detect in a robust way? What to do with that? Maybe there are similar things that could break?

Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent