You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As shown by the comparison of mode splits from kpi-modal-split.csv1 compared against mode splits from elara trip_logs_all_trips.csv. Most modes line up, except for bus and rail with slightly higher values in gelato vs. lower walk split.
I think both Gelato and Elara are supposed to be calculating dominant mode of a trip based on longest distance so unsure why we're getting these slight differences across bus, rail and walk.
The text was updated successfully, but these errors were encountered:
The kpi-modal-split.csv outputs are created based on the analysis tabular dataoutput_trips.csv.
The method for extracting trip information in matsim can indeed be differentiated based on whether the source is the output events file or the output plans file. Elara illustrates a method for parsing the output_plans.xml file. In contrast, matsim's built-in functionality for generating output_trips.csv typically involves analyzing the output_events.xml file.
The discrepancy between the longest distance mode as defined by elara (bus) and the matsim output (rail) arise from differences in how distances are calculated or aggregated. I have checked the specific agent in the output plans and event files.
Elara trip is summing distances for all legs(code) and considering the mode with the highest sum as the longest distance mode. So I believe the mode is defined based on total cumulative distance across all legs
The matsim trip, derived from events, reflect the actual distances travelled by each mode in a single trip in one leg.
I think both methods could be "correct" depending on the analytical perspective.
I'll be closing this issue as the differences are addressed in issue 57 and the fact that gelato is using the trips file whereas Elara uses plans. We'll need to understand the usefulness of generating trips data from the plans file at a future stage.
Comments apply to TE simulation
As shown by the comparison of mode splits from
kpi-modal-split.csv1
compared against mode splits from elaratrip_logs_all_trips.csv
. Most modes line up, except forbus
andrail
with slightly higher values in gelato vs. lowerwalk
split.I think both Gelato and Elara are supposed to be calculating dominant mode of a trip based on longest distance so unsure why we're getting these slight differences across
bus
,rail
andwalk
.The text was updated successfully, but these errors were encountered: