ISAT Demonstration Scenarios

About the ISAT Demonstration Scenarios

Making something happen during a simulation in a repeatable and consistent fashion for different driving styles is the essence of scenario authoring. Every thing that happens must be coordinated to some degree with the External Driver (XD). For repeatability, it is also necessary to consider how different driving styles (aggressive vs. conservative) impact how the scenario unfolds for each.

These demonstration scenarios were created to facilitate learning how to use ISAT and do scenario actions. Each scenario demonstrates a key concept or element and may contain additional elements to support the main concept. For example, all scenarios contain an introduction to the scenario for the XD and a termination trigger that will stop the simulation.

These scenarios are not intended for use as completed data collection ready scenarios. They are provided to answer the question "how can I do X Y Z..?"

These scenario elements can be integrated into your scenarios using copy-paste except where elements have been created with a Create action. For those elements it will be necessary to copy the parent element instead.

Demo_ISAT_ADO_Control.scn

This scenario demonstrates how to control an ADO:

• ADO set dial > forced velocity = 0 to keep ADO stationary. • Release the forced velocity, assign a maintain gap. • Release the maintain gap, assign a target velocity.

See also: Demo_ISAT_ADO_Forced_Velocity_Sum_of_Sines.scn Demo_ISAT_ADO_Oncoming_Incursion.scn Demo_ISAT_ADO_TTA_LVPO.scn

Demo_ISAT_ADO_Forced_Velocity_Sum_of_Sines.scn

This scenario demonstrates how to vary the velocity of an ADO using a Sum of Sines expression:

• Uses a forced velocity action; • Try to maintain a constant speed at 30 mph; • Notice how the speed of the ADO changes during the drive.

Note: • There is also a forced velocity Sin function available with 4 parameters See Also: Demo_ISAT_ADO_Control.scn Demo_ISAT_ADO_Oncoming_Incursion.scn Demo_ISAT_ADO_TTA_LVPO.scn

Demo_ISAT_ADO_Oncoming_Incursion.scn

This scenario demonstrates the use of a forced lane offset to cause an oncoming ADO to veer into the driver’s lane:

• Additional ambient traffic is included to provide a normal driving environment; • A following ADO will encourage slow drivers to travel the speed limit; • Because we do not want to rely on the driver travelling at the right speed, we match the event ADO velocity to the driver to ensure the event happens as planned.

See Also: Demo_ISAT_ADO_Control.scn Demo_ISAT_ADO_Forced_Velocity_Sum_of_Sines.scn Demo_ISAT_ADO_TTA_LVPO.scn

Demo_ISAT_ADO_Passing_Maneuvers.scn

This scenario demonstrates how to implement an ADO passing maneuver on 4 lane and 2 lane roads:

• 4 lane roads can use either Set Dial > ADO > Lane Change OR Set_Button > ADO > Lane Change; • Lane change actions are not supported on 2 lane roads; - Use a lane offset to produce something similar to a passing maneuver

Demo_ISAT_ADO_Random.scn

This scenario demonstrates how to use the Rand() function to assign a randomized gap to an ADO:

• Typical gap assignments are fixed/constant; • Use of a randomized value introduces some inconsistency to the ADO position, which is organic and more realistic. • Requires the use of variables and expressions. • Saves the calculated randomizations to the DAQ for validation (review in ISAT).

See also: Demo_ISAT_ADO_Control.scn Demo_ISAT_ADO_Forced_Velocity_Sum_of_Sines.scn Demo_ISAT_ADO_TTA_LVPO.scn

Demo_ISAT_ADO_Relative_Create.scn

This scenario demonstrates how to use the Relative Create flag for ADOs.

Note: Relative Create works only with negative values.

Used to create traffic behind the external driver independent of the location where the ADOs are initially placed.

ISAT Demonstration Scenarios

Contents