Skip to content
GitLab
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
    • Graph
    • Compare
    • Locked Files
  • Issues 93
    • Issues 93
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse ProjectsEclipse Projects
  • Eclipse ESCET (Supervisory Control Engineering Toolkit)
  • escet
  • Issues
  • #116
Closed
Open
Issue created Jun 10, 2021 by Ferdie Reijnen@freijnenDeveloper

Reconsider requirement warnings when simulating.

When simulating a CIF file, a warning is printed for every automaton and invariant with a requirement kind. For each invariant the following text is printed:

 WARNING: Invariant <inv> of group <group> is a requirement, but will be simulated as a plant.

It is not uncommon for a file to have 100+ requirement invariants, and the whole console output will be filled with warnings.

This has two downsides:

  1. Important warnings may be overlooked.
  2. It looks unprofessional when demonstrating the simulation.

Why don't we generate only one warning?

 WARNING: The specification contains requirements, these will be simulated as plants.
Edited Jun 10, 2021 by Ferdie Reijnen
Assignee
Assign to
Time tracking

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