Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
JPScore
JPScore
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 92
    • Issues 92
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • 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
  • JuPedSim
  • JPScoreJPScore
  • Issues
  • #268

Closed
Open
Opened Mar 26, 2018 by benjamin moehring@moehring1Maintainer

Make escalators direction-dependent

Short description of suggestion

JuPedSim allows us to define subrooms as "stairs" or "escalators". So far the escalator only influences an agent's speed, defined by the parameters

  • v0_escalator_upstairs mu="0.5" sigma="0.0"/
  • v0_escalator_downstairs mu="0.5" sigma="0.0"/

However, the direction of an escalator isn't considered in the routing. This mean that agents can take escalators in the wrong direction.

How to change this:

Talking to Arne and Mohcine, we figured out a way that could possibly work.

  • class="escalator"

has to be further specified by:

  • class="escalator_up"
  • class="escalator_down"

After initializing the distance_matrix the distance value in the forbidden direction has to be changed to a very large value for each escalator. The subroom is then unlikely to be chosen.

Best, Benni

Edited Mar 26, 2018 by benjamin moehring
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: jupedsim/jpscore#268