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
  • Issues
  • #51

Closed
Open
Created Feb 05, 2018 by Stefan Schuhbaeck@stscMaintainer

An update of the Source ID update is only recocnized in the PedestrianSourceIdProcessor after restart of application

If Vadere is started and the PedestrianSourceIdProcessor is present or is added the sourceId column is added to the PedestrianIdKey Outputfile as expected. If the sourceId is then changed in the Topography builder and a second simulation run is done. Only the new simulation is highlighted green in the output table (as expected because the Scenario changed) but in the output file the old sourceId is used.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking