Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Flatland Flatland
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Flatland
  • FlatlandFlatland
  • Issues
  • #255

Closed
Open
Created Oct 23, 2019 by Erik Nygren@mlerik🚅Owner

Synchronization of agent steps

Story

As a Project Member, I want to discuss and update the way steps are executed in agents. Currently each agents action is executed squentially. This means that optimizers struggle to find optimal solutions as there is an asymmetry introduced by the agent index. We want to change this behavior by removing this assymetry by either:

  • There is a minimal release time of each cell (e.g. 1 step). This means that a new agent can only enter a cell when the previous cell has been empty for at least one time step.
  • We test for all legal actions sequentially and only update the agent true position after all agents have performed their tests. This however will introduce potential conflicts where multiple agents want to enter the same cell at the same time. This could be regarded as a crash and environment would terminate. This is too much of a change for the current running challenge

Acceptance Criteria

  • We agree as a team on what way to go
  • We open an issue to resolve the problem by implementing the discussed solution
Assignee
Assign to
Time tracking