Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
A
AF3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 258
    • Issues 258
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • af3
  • AF3
  • Issues
  • #3691

Closed
Open
Opened Mar 21, 2019 by Alexander Diewald@diewaldGuest

Extend the DseML to enable specifying non-existing model elements

The exact strategy to resolve this issue has yet to be clarified.

The idea is to enable the DseML to specify expressions on non-yet existing model elements (i.e., they are created by the solver). Here, it has to be examined if it is sufficient to specify a “VariableModelElementLiteral” or if the Set definition also has to be adapted. Furthermore, it has to be clarified if unbound sets shall be supported.

(from redmine: issue id 3691, created on 2019-03-21)

  • Relations:
    • parent #3689
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: af3/af3#3691