• TripInfo

Instantiating within the Simulation#

The simulation is forced to generate this output using the option --tripinfo-output <FILE> on the command line/within a configuration. This output contains the information about each vehicle's departure time, the time the vehicle wanted to start at (which may be lower than the real departure time) and the time the vehicle has arrived. The information is generated for each vehicle as soon as the vehicle arrived at its destination and is removed from the network.

Generated Output#

The format is as following:

<tripinfos>
    <tripinfo id="<VEHICLE_ID>" \
            depart="<DEPARTURE_TIME>" departLane="<DEPARTURE_LANE_ID>" \
            departPos="<DEPARTURE_POSITION>" departSpeed="<DEPARTURE_SPEED>" \
            departDelay="<DEPARTURE_DELAY>" \
            arrival="<ARRIVAL_TIME>" arrivalLane="<DEPARTURE_LANE_ID>" \
            arrivalPos="<ARRIVAL_POSITION>" arrivalSpeed="<ARRIVAL_SPEED>" \
            duration="<TRAVEL_TIME>" routeLength="<ROUTE_LENGTH>" \
            waitingTime="<SECONDS_WAITING_FOR_TRAFFIC>"
            waitingCount="<NUMBER_OF_WAITING_EPISODES>" \
            rerouteNo="<REROUTE_NUMBER>" \
            devices="<DEVICE_LIST>" vtype="<VEHICLE_TYPE_ID>"/>

    ... information about further vehicles ...

</tripinfos>

Please note that, in contrary to the example above, for each time step, all those values are reported in one line. An entry is written each time a vehicle has arrived at his destination. In prior to this, the written values would not be known.

Devices#

Single devices may choose to add further output to the tripinfo file.

Emissions#

The "emissions" device instantiated using one of the options --device.emissions.probability <FLOAT> or --device.emissions.explicit <ID>[,<ID>]*. The written emissions depend on the chosen emission class of the vehicle (see Definition of Vehicles, Vehicle Types, and Routes and Models/Emissions) contributes to the tripinfo output. It provides the sum of all emissions/consumption generated/consumed by the vehicle during its journey.

This adds the following line:

<tripinfos>
    <tripinfo id="<VEHICLE_ID>" ... vtype="<VEHICLE_TYPE_ID>">
        <emissions CO_abs="..." CO2_abs="..." HC_abs="..." PMx_abs="..." NOx_abs="..." fuel_abs="..."/>
    </tripinfo>
    ... information about further vehicles ...

</tripinfos>

with units as following

Battery#

The "battery" device contributes to the tripinfo output how many times the vehicle encountered its battery depleted during its journey. Vehicles can be forced to stop due to lack of energy using the "stationfinder" device or may recuperate energy while braking and then deplete the battery again.

This adds the following line:

<tripinfos>
    <tripinfo id="<VEHICLE_ID>" ... vtype="<VEHICLE_TYPE_ID>">
        <battery depleted="..."/>
    </tripinfo>
    ... information about further vehicles ...

</tripinfos>

with the attributes as following

Output for vehicles that have not arrived at simulation end#

By default, tripinfo-output is only written on vehicle arrival. This means vehicles that have not arrived at simulation end (i.e. due to option --end) generate no output. To change this, the option --tripinfo-output.write-unfinished can be used.

Output only for selected vehicles or vehicle types#

By default all vehicles will generated tripinfo-output. By assigning a tripinfo device to selected vehicles or types, this can be changed.

Example: Setting SUMO-option --device.tripinfo.probability 0 will disable the device for all vehicles by default. The following definition overrides this default end enables the device for busses:

<vType id="bus">
  <param key="has.tripinfo.device" value="true"/>
</vType>

Person and Container Output#

If the simulation contains persons or containers, the following elements will be added to the output:

<personinfo id="person0" depart="0.00">
 <walk depart="0.00" arrival="47.00" arrivalPos="55.00"/>
 <ride waitingTime="74.00" vehicle="train0" depart="121.00" arrival="140.00" arrivalPos="92.00"/>
 <stop duration="20.00" arrival="160.00" arrivalPos="45.00" actType="singing"/>
</personinfo>

<containerinfo id="container0" depart="0.00">
  <tranship depart="0.00" arrival="54.00" arrivalPos="55.00"/>
  <transport waitingTime="103.00" vehicle="train0" depart="157.00" arrival="176.00" arrivalPos="92.00"/>
  <stop duration="20.00" arrival="196.00" arrivalPos="40.00" actType="waiting"/>
</containerinfo>

When setting option --personinfo-output FILE, the above elements will be written to the given filename instead of written together with the vehicle <tripinfo> elements.

The <personinfo> / <containerinfo> attributes have the following meaning:

The attributes within the stages have the following meaning:

Aggregated Output#

Aggregated output for key tripinfo-output attributes can be obtained by setting the option --statistic-output.

For further aggregation see attributeStats.py and Tools/Xml#xml2csv.py.

Visualization Examples#

The TripInfo output can be used as input for several visualization tools shipped with SUMO. Some example plots are shown below.

Depart delays over time#

Generated with plotXMLAttributes.py.

Histogram of the number of stops#

Generated with plot_tripinfo_distributions.py.