-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get the total travel time for each link in the network #1162
Comments
Hello, Can anyone answer my questions? Is there a way to modify the config file so that the total travel time for each link can be shown in output files? Thank you. Yours sincerely, |
Hi, have a look into your iteration output directories for the ..linkstats.txt.gz. It contains travel time statistics for every hour (but not the sum of all travel times neither the volume, I think).
The easiest way to what you want might be running LinkStats class in matsim-libs as a postprocess. In case you have a scenario which is setup in the Alternatively, you can program that yourself via an own implementation of Another way would be to load output events and network into Via and then make it compute average volumes and speeds (click on the network properties -> Link Attributes -> Add...) and then potentially export the network, if needed. If you are rather interested in avrage speeds and volumes, you can also add the |
Hello, I can the columns like TRAVELTIME2-3avg indicates that the time for one vehicle to pass a link. So perhaps TRAVELTIME2-3avg times HRS2-3avg is the total time that all vehicles spent on each link during hours 2-3. However, it seems that the results for different iterations are different. I don't know the event output file is related to which iteration. Can anyone tell me? In addition, how to use LinkStats class in matsim-libs to do the postprocessing? |
Hello,
Could anybody tell me after running the MATSIM, how to get the total travel time on each link in the network? Thank you.
The text was updated successfully, but these errors were encountered: