Difference between revisions of "Simulation/Output/SSM Device"

From Sumo
Jump to navigation Jump to search
(Created page with "A vehicle can be equipped with an SSM Device which logs the conflicts of the vehicle and other traffic participants (currently only vehicles) and corresponding safety surrogat...")
 
Line 1: Line 1:
 
A vehicle can be equipped with an SSM Device which logs the conflicts of the vehicle and other traffic participants (currently only vehicles) and corresponding safety surrogate measures.
 
A vehicle can be equipped with an SSM Device which logs the conflicts of the vehicle and other traffic participants (currently only vehicles) and corresponding safety surrogate measures.
 +
 +
# Equipping vehicles
 +
To attach an SSM device to a vehicle, the [[Definition_of_Vehicles,_Vehicle_Types,_and_Routes#Devices|standard device-equipment procedures]] can be applied using <code><device name>=ssm</code>.
 +
 +
For instance, a single vehicle can be equipped (with a device parametrized by default values) as in the following example
 +
 +
<pre class="xml">
 +
<routes>
 +
    ...
 +
    <vehicle id="v0" route="route0" depart="0">
 +
        <param key="has.ssm.device" value="true"/>
 +
    </vehicle>
 +
    ....
 +
</routes>
 +
</pre>
 +
 +
The SSM device generates an output file (one for each vehicle named <code>ssm_<vehicleID>.xml</code> per default, but several vehicles may write to the same file). The top level elements of the generated file are <code><conflict begin="<log-begin-time>" end="<log-end-time>" ego="<equipped-vehicleID>" foe="<opponent-vehicleID>"> ... </conflict></code>.
 +
 +
The SSM device supports output-customization by a range of parameters.

Revision as of 12:13, 26 July 2017

A vehicle can be equipped with an SSM Device which logs the conflicts of the vehicle and other traffic participants (currently only vehicles) and corresponding safety surrogate measures.

  1. Equipping vehicles

To attach an SSM device to a vehicle, the standard device-equipment procedures can be applied using <device name>=ssm.

For instance, a single vehicle can be equipped (with a device parametrized by default values) as in the following example

<routes>
    ...
    <vehicle id="v0" route="route0" depart="0">
        <param key="has.ssm.device" value="true"/>
    </vehicle>
    ....
</routes>

The SSM device generates an output file (one for each vehicle named ssm_<vehicleID>.xml per default, but several vehicles may write to the same file). The top level elements of the generated file are <conflict begin="<log-begin-time>" end="<log-end-time>" ego="<equipped-vehicleID>" foe="<opponent-vehicleID>"> ... </conflict>.

The SSM device supports output-customization by a range of parameters.