Skip to content
GitLab
Projects Groups Topics 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
    • Graph
    • Compare revisions
    • Locked files
  • Issues 99
    • Issues 99
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse ProjectsEclipse Projects
  • Eclipse ESCET (Supervisory Control Engineering Toolkit)
  • escet
  • Issues
  • #140

CIF to CIF Remove requirements removes too much information.

Consider the following specification:

input bool X;
event c_on;

requirement p:
  plant invariant c_on needs X;
  location:
    initial;

end

Removing requirements results in:

input bool X;
event c_on;

Notice that the plant invariant is also removed. This should not happen.

We should add as a restriction that requirement automata may not contain kindless, plant, or supervisor invariants.

Alternatively, we could move the non-requirement invariants outside of locations to the parent group/specification. Location invariants can never be supported as the locations are removed and we cannot refer to them.

Edited Jul 07, 2021 by Ferdie Reijnen
Assignee
Assign to
Time tracking

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