Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • V vadere
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 118
    • Issues 118
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • vadere
  • vadere
  • Merge requests
  • !184

Merged
Created Mar 23, 2022 by Christina Maria Mayr@christina-maria-mayrMaintainer

Check distance between obstacles for narrow bottlenecks.

  • Overview 5
  • Commits 6
  • Pipelines 3
  • Changes 6

Sometimes agents get stuck in front of corridors.

vadere_2022_03_11_12_27_13

Reason: the global minimum (within walking distance) is in front of the corridor.

The smaller the corridor, the more likely is it that agents get stuck. One option is to adjust the attributes of the floorfield, in particular, the parameter targetAttractionStrength. See AttributesFloorField for details.

To make users aware of this problem I extended the scenario checker. It gives a warning if obstacles have a distance less 1.28m. If obstacles are connected, the distance is 0. If so, the scenario checker does not produce a warning, see example below.

Limitation

The agent A is stuck in front of the corridor. The target T is on the right. Left: the bottleneck is identified. A user warning is produced including the distance c. Right: no warning is produced.

Edited Mar 23, 2022 by Christina Maria Mayr
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: agents_unclogged