Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
V
vadere
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 111
    • Issues 111
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 4
    • Merge Requests 4
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • vadere
  • vadere
  • Issues
  • #201

Closed
Open
Opened Jan 18, 2019 by Daniel Lehmberg@hm-lehmbergMaintainer

Dataprocessing: multiple processors writing out to one file have same header name

Summary

Screenshot_from_2019-01-18_09-59-01

Like in the screenshot, processor 1 and 6 write to the same file (each processor may have different settings). In the .csv file the top looks like this:

timeStep pedestrianId countingDensity countingDensity
1 1 3.2538343921009716 2.5464790894703255
1 2 2.4050080289441964 1.6269171960504858
1 3 2.2635369684180673 1.6976527263135504

So there is a header naming issue and there is no reassurance which column belongs to which processor.

What is the expected correct behavior?

Handle name mangling in this case!

Edited Jan 18, 2019 by Daniel Lehmberg
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: vadere/vadere#201