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

From Sumo
Jump to navigation Jump to search
m
Line 4: Line 4:
 
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>.
 
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
+
For instance, a single vehicle can be equipped (with a device parametrized by default values) as in the following minimal example
  
 
<pre class="xml">
 
<pre class="xml">
Line 16: Line 16:
 
</pre>
 
</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 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  
  
The SSM device supports output-customization by a range of parameters.
+
<code><conflict begin="<log-begin-time>" end="<log-end-time>" ego="<equipped-vehicleID>" foe="<opponent-vehicleID>"> ... </conflict></code>.
 +
 
 +
The detail of information given for each conflict and the criteria to qualify an encounter as a conflict (i.e., produce a corresponding <code>conflict</code> element in the output) can be customized by a number of generic parameters to the vehicle or device, resp.. A full parametrization (redundantly assigning the default values, here) could look as follows:
 +
 
 +
<pre class="xml">
 +
<routes>
 +
    ...
 +
    <vehicle id="v0" route="route0" depart="0">
 +
        <param key="has.ssm.device" value="true"/>
 +
        <param key="device.ssm.measures" value="TTC DRAC PET"/>
 +
        <param key="device.ssm.thresholds" value="3.0 4.0 2.0"/>
 +
        <param key="device.ssm.range" value="50.0" />
 +
        <param key="device.ssm.extratime" value="5.0" />
 +
        <param key="device.ssm.file" value="ssm_v0.xml" />
 +
        <param key="device.ssm.trajectories" value="false" />
 +
        <param key="device.ssm.geo value="false" />
 +
    </vehicle>
 +
    ....
 +
</routes>
 +
</pre>

Revision as of 12:21, 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 minimal 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 detail of information given for each conflict and the criteria to qualify an encounter as a conflict (i.e., produce a corresponding conflict element in the output) can be customized by a number of generic parameters to the vehicle or device, resp.. A full parametrization (redundantly assigning the default values, here) could look as follows:

<routes>
    ...
    <vehicle id="v0" route="route0" depart="0">
        <param key="has.ssm.device" value="true"/>
        <param key="device.ssm.measures" value="TTC DRAC PET"/>
        <param key="device.ssm.thresholds" value="3.0 4.0 2.0"/> 
        <param key="device.ssm.range" value="50.0" />
        <param key="device.ssm.extratime" value="5.0" />
        <param key="device.ssm.file" value="ssm_v0.xml" />
        <param key="device.ssm.trajectories" value="false" />
        <param key="device.ssm.geo value="false" />
    </vehicle>
    ....
</routes>