Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • dml-solving dml-solving
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Descartes Research
  • dml-solvingdml-solving
  • Issues
  • #9

Closed
Open
Created Aug 18, 2017 by Chair of Software Engineering@info2Owner

Implemented model composition step may 'truncate' requested probes

The current implementation of the model composition step (see edu.kit.ipd.descartes.solving.tailoring.TailoredModelComposition) may 'truncate' requested probes.

For example: If the default service behavior abstraction level is set to black box, and there is a service with two service behavior abstractions (fine- or) coarse-grained and black box, the black box behavior will get selected even if there were, e.g., some resource utilization probes that would have been affected by the (fine- or) coarse-grained behavior, but are not affected by the black box behavior.

See Fabian's PhD for a model composition algorithm, that takes such potential conflicts into account.

Assignee
Assign to
Time tracking