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
  • #3769

Closed
Open
Opened Dec 05, 2020 by Dummy AF3-Dev@dummy-af3-dev

Adapt scheduling constraints to take advantage of alternative routes

Currently the SMT constraints for the schedule synthesis rely on a fixed allocation of Signals to Routes. While this allocation has been trivial under the assumption that each pair of communication ECUs is connected by one route only, #3768 (closed) defines multiple alternative shortest routes.

As of now, if there are more than one shortest paths between two communicating ECUs, the respective signal is randomly assigned to one of the available routes in org.fortiss.af3.exploration.smt.util.AllocationToSchedule.createSignals(SystemSchedule, Task, SuperSet<TaskToExecutionUnitAllocationEntry>, SuperSet<Route>, Map<Route, SignalToRouteAllocationEntry>). Hence, in order to take advantage of alternative routes when generating a schedule, the generation of constraints has to be adapted such that the allocation of signals to routes is not fixed beforehand, but is left to the solver.

(from redmine: issue id 3769, created on 2019-07-09)

  • Uploads:
    • AF3-Project.af3_23 Minimal AF3 project for testing
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: af3/af3#3769