Simulation Output Data

Main Page > Technical Documentation > Simulation Output Data

Multiple output files can be selected for output, as selected from the simulation control panel. These files get written to the output data folder selected in the project properties dialog. The various performance measures included in these output files are described in the Performance Measures section.

Link Performance Measure Data

Outputs link-wide performance measures, to a comma-separated value (CSV) file. The CSV file will be named as follows:

"LinkResults.csv"

The LinkResults.csv will contain the following information:
 * Scenario
 * SubScenario
 * Replication
 * Link Id
 * Density (veh/mi/ln)
 * Speed (mi/h)
 * Flow Rate (veh/h/ln)
 * Num. Passenger Cars
 * Percentage of Passenger Cars
 * Num. SUT (Single Unit Truck)
 * Percentage of SUT
 * Num. IMST (Intermediate Semi-Trailer)
 * Percentage of IMST
 * Num. ISST (Interstate Semi-Trailer)
 * Percentage of ISST
 * Num. DST (Double Trailer Semi-Trailer)
 * Percentage of DST
 * Total Num. Vehicles
 * Veh. Hours traveled (veh-h)
 * Veh. Miles traveled (veh-mi)
 * Delay Left Turn Vehicles (veh-s)
 * Delay Through Vehicles (veh-s)
 * Delay Right Turn Vehicles (veh-s)
 * Volume Left Turns (veh)
 * Volume Through (veh)
 * Volume Right Turns (veh)
 * Total Stops

Detector Aggregate Measures Data

Outputs aggregated detector measured values, for all network detectors, to a comma-separated value (CSV) file. The CSV file will be named as follows:

"DetectorAggregateMeasures_ProjectName.csv"

where ProjectName will correspond to the name of your currently loaded project file (i.e., the *.ssim file).

This (CSV) file will contain the following information


 * Scenario
 * SubScenario
 * Replication
 * Link ID
 * Lane ID
 * Detector ID
 * Detector Function (e.g., signalized, ramp meter)
 * Detector Label
 * Veh. Count Total
 * Flow rate (veh/h)
 * Avg. Speed (mi/h)
 * Avg. Speed (ft/s)
 * Avg. Headway (s)
 * Percent Followers
 * Follower Density
 * FHWA Class 1-13 Totals [FHWA classification]
 * Veh. Type 1-13 Totals Vehicles

Note that detector actuations that occur during the warm-up time are not included in the results reported in this file.

Detector Vehicle Actuation Data Outputs details of each detector actuation, for all network detectors. One comma-separated value (CSV) file will be created for each detector. Each CSV file will be named as follows:

"Link_i_Lane_j_Detector_k_x_z.csv"

where: i corresponds to the Link ID of the link containing the detector, j corresponds to the Lane ID of the lane containing the detector, k corresponds to the Detector ID, x corresponds to the scenario number, and z corresponds to the replication number.

The (CSV) file will contain the following information.


 * The following values are fixed for each file; thus, they are printed just once at the top of the file.
 * Link ID
 * Lane ID
 * Detector ID
 * Detector Label
 * Travel Direction


 * The following values are unique to each vehicle actuation; thus, they will change from one row (record) to the next.
 * Vehicle ID
 * Actuation Time: time when front of vehicle passes detector's upstream edge
 * FHWA Class[FHWA classification]
 * Speed (mi/h)
 * Gap (ft)
 * Headway (s)
 * Queue Status
 * Assignment turning movement at link end

Note that all detector actuations, during and after the warm-up time, are included in the results reported in this file.

Lane Change Data

Outputs details of the lane change maneuvers, to a comma-separated value (CSV) file.

The (CSV) file will contain the following information


 * Vehicle ID
 * Time Index
 * Link ID
 * Lane Change Motivation
 * Future Passing Mode
 * Desired Lane ID
 * Subject Vehicle Makes a lane change?
 * Subject Vehicle Link Position
 * Subject Vehicle Velocity
 * Subject Vehicle Acceleration
 * Subject Vehicle Urgency Factor
 * Subject Vehicle Acceptable Risk
 * ID of Lead Vehicle on Desired Lane
 * ID of Following Vehicle on Desired Lane
 * Velocity of Lead Vehicle on Desired Lane
 * Velocity of Following Vehicle on Desired Lane
 * Distance between Subject Vehicle and Lead Vehicle on Desired Lane
 * Distance between Following Vehicle on Desired Lane and Subject Vehicle
 * Actual Risk of Subject Vehicle with Respect to Lead Vehicle on Desired Lane
 * Actual Risk of Follow Vehicle on Desired Lane with Respect to Subject Vehicle
 * Subject Vehicle Is Able to Avoid Collision with Lead Vehicle on Desired Lane?
 * Follow Vehicle on Desired Lane Is Able to Avoid Collision with Subject Vehicle?
 * Lead Gap Is Acceptable?
 * Lag Gap Is Acceptable?

Platoon Data Outputs vehicle platoon measurements, to a comma-separated value (CSV) file.

Emissions and Fuel Consumption Data The simulation will calculate detailed vehicle emissions and fuel consumption data, for every simulation time step. These values can be viewed in the animation, as well as the vehicle time step data output file (if selected for output).

Vehicle Headway Data Outputs the headway values for each vehicle generated into the network, from each entry node, to a comma-separated value (CSV) file. The CSV file will be named as follows:

"HeadwayDataOutput.csv"

The (CSV) file will contain the following information


 * Node ID
 * Vehicle ID
 * Original Headway Value
 * Revised Headway Value

Vehicle Time Step Data Outputs detailed vehicle data, for every simulation time step, to a comma-separated value (CSV) file. These values can also be viewed in the animation when individual vehicle properties are displayed. The file is named “TSD__x_y_z”, where x corresponds to the scenario number, y corresponds to the sub-scenario number, and z'' corresponds to the replication number. The file provides detailed time-step vehicle properties. Keep in mind that this file can get extremely large if many network links are selected for output, so it is generally recommended to output only the links for which you need to do a close examination of the vehicle properties and/or want to do some post-processing of the data.

The (CSV) file will contain the following information (with units, as appropriate, in parentheses), in order from left to right as the fields are presented in the file:


 * 1) SimTime (s)
 * 2) Veh Index
 * 3) Fleet Type
 * 4) Veh Label
 * 5) Veh Length (ft)
 * 6) Veh Width (ft)
 * 7) Driver Type
 * 8) Link ID
 * 9) Target Link ID
 * 10) Lane ID
 * 11) Target Lane ID
 * 12) Lane Change Status
 * 13) Passing Status
 * 14) Leader ID
 * 15) Follow ID
 * 16) Platoon Position
 * 17) Acceleration Mode
 * 18) Acceleration (ft/s/s)
 * 19) Desired Acceleration (ft/s/s)
 * 20) Velocity (ft/s)
 * 21) Desired Speed
 * 22) PositionX (ft)
 * 23) PositionY (ft)
 * 24) Angle (deg)
 * 25) Link Position (ft)
 * 26) Distance To Lead Vehicle (ft)
 * 27) System Entry Time (s)
 * 28) System Exit Time (s)
 * 29) Cold Start
 * 30) Vehicle Specific Power (VSP)
 * 31) Nitrogen Oxide (NOx)
 * 32) HydroCarbons (HC)
 * 33) Carbon Monoxide (CO)
 * 34) Fuel Use
 * 35) Manifold Pressure
 * 36) Mass Air Flow
 * 37) Engine Load
 * 38) Gear
 * 39) Gear Ratio
 * 40) RPM
 * 41) Torque (ft-lb)
 * 42) Power (ft-lb/s)
 * 43) Latitude
 * 44) Longitude
 * 45) Lane ID Right
 * 46) Lane ID Left
 * 47) Queue Status

Signal Time Step Data

Generates a CSV file named “TSD_signal.csv” upon running a simulation. The file provides the signal phase status for every simulation time step, for every signal in the network, to a comma-separated value (CSV) file.

The (CSV) file will contain the following information


 * Signal ID
 * Simulation Time
 * Phase Number
 * Status
 * Interval
 * Time Remain

Ramp Metering Data Outputs details of the ramp metering controller and its associated control detectors. One comma-separated value (CSV) file will be created for each ramp metering controller. Each CSV file will be named as follows:

"RampMeteringIntervalData_ControllerId_k_x_y_z.csv"

where: k corresponds to the ramp controller ID, x corresponds to the scenario number, y corresponds to the subscenario number, and z corresponds to the replication number.

The (CSV) file will contain the following information:
 * Time(s): This will be in 30-s increments, which is the ramp metering rate calculation update interval
 * Ramp Controller ID: These values correspond to ID value in signal timing data file
 * Controller Phase ID: The number of phase ID’s will correspond to the number of lanes served
 * Metering Rate (veh/h): Calculated metering rate. If more than one lane is controlled by meter (which means there will be more than one phase ID), the metering rate is divided by the number of lanes. For example, if the metering rate is set of a minimum value of 240 veh/h, and meter serves two lanes, the metering rate per phase will be set to 120 veh/h. The proportional split of the overall metering rate between the phases can be changed by the user, but by default, is split evenly across the number of lanes (e.g., 0.5 for two metered lanes).

There will only be one instance of the above four column headings. The following column headings will repeat for each detector associated with the given ramp controller phase ID, as follows.


 * Det Link ID: Link on which detector is present
 * Det Lane ID: Lane on which detector is present
 * Det ID: ID number for detector
 * Det Function: This will be either…
 * RampMeterPresence: Detector immediately upstream of ramp meter stop bar
 * RampMeterQueueIntermediate: Detector placed approximately 500 ft upstream of ramp meter stop bar
 * RampMeterQueueAdvance: Detector placed near the arterial/on-ramp junction
 * Det Occ Interval(%):
 * Det Occ Cumulative(%):

A "RampMeteringSummaryData.csv" file is also output. This file provides the percentage of time, over the simulation period, that the metering rate was set to one of three values (base, intermediate queue, advance queue).