Introduction

SUMO allows to generate a large number of different measures. All write the values they collect into files or a socket connection following the common rules for writing files. Per default, all are disabled, and have to be triggered individually. Some of the available outputs (raw vehicle positions dump, trip information, vehicle routes information, and simulation state statistics) are triggered using command line options, the others have to be defined within "additional files".

Available Output Files

Below, the available outputs are listed, joined into groups of topic/aggregation type. Further information about each output can be found by following its link.

vehicle-based information, unaggregated

• raw vehicle positions dump: all vehicle positions over time
  contains: positions and speeds for all vehicles for all simulated time steps
  used for: obtaining movements of nodes (V2V, for ns-2)
• vehicle type probe: positions of vehicles over time for a certain vehicle type (or all vehicles)
• emission output: emission values of all vehicles for every simulation step
• full output: various informtations for all edges, lanes and vehicles (good for visualisation purposes)
• vtk output: generates Files in the well known VTK (Visualization Toolkit) format, to show the positions the speed value for every vehicle
• fcd output: Floating Car Data includes name, position, angle and type for every vehicle
• trajectories output: Trajectory Data following includes name, position, speed and acceleration for every vehicle following the Amitran standard

simulated detectors

• inductive loop detectors: simulated induction loops
• instant induction loops: simulated unaggregated induction loops
• areal detectors: lanearea detectors - simulated vehicle tracking cameras
• entry/exit detectors: simulated entry/exit detectors

values for edges or lanes

• edgelane traffic: edge/lane-based network performance measures
• aggregated Amitran measures: edge/lane-based network performance measures following the Amitran standard
• edgelane emissions: edge/lane-based vehicular pollutant emission
• edgelane noise: edge/lane-based vehicular noise emission; based on Harmonoise
• queue output: lane-based calculation of the actual tailback in front of a junction

vehicle-based information

• trip information: aggregated information about each vehicle's journey
• vehicle routes information: information about each vehicle's routes over simulation run
• battery usage: information about battery state for electric vehicles

simulation(network)-based information

• simulation state statistics: information about the current state of the simulation

traffic lights-based information

• traffic light states: information about the state (lights) of a traffic light
• stream-based traffic light switches: information about the switches of a traffic light signal responsible for a certain link
• traffic light states, by switch: information about the states (lights) of a traffic light signal, written only when changed
• areal detectors coupled to tls: simulated vehicle tracking cameras triggered by tls

Additional Debugging Outputs

• The option --link-output <FILE> saves debugging data for the intersection model. This data reveals how long each vehicle intends to occupy an upcoming intersection.
• The option --movereminder-output <FILE> saves debugging data for the interaction between vehicle devices, lanes and output facilities. It is only available when compiling SUMO with debug flags.

Commandline Output (verbose)

• Inserted: number vehicles that entered the simulation network
• Loaded: number of vehicles that were loaded from route files. This may differ from emitted forw two reason:
  • Running with option --scale with a value less than 1.0
  • Having a congested network where not all vehicles could be inserted before the simulation time ended
• Running: number of vehicles currently active in the simulation network
• Waiting: number of vehicles which could not yet be inserted into the network due to congestion
• Teleports: number of of times that vehicles were teleported for any of the following reasons (These reasons are given whenever a teleport warning is issued)
  • Collision: a vehicle violated its minGap requirement in relation to its leader vehicle
  • Timeout: a vehicle was unable to move for --time-to-teleport seconds (default 300)
    • wrong lane: a vehicle was unable to move because it could not continue its route on the current lane and was unable to change to the correct lane
    • yield: a vehicle was unable to cross an intersection where it did not have priority
    • jam: a vehicle could not continue because there was no space on the next lane