Run the Test
Start, Stop and Reset a Test
Online Test
When you are ready to begin a test, press the test START button. Test Suite will begin logging data straight away, but the test will not start until you press the trigger to signify TAway. TAway is the time when the driver's eye finds the gaze location (camera 2 when using this methodology). This is manually defined by pressing the handheld trigger.
This gives you time to prepare the vehicle and achieve a steady state before beginning the test by pressing the trigger.
Press the trigger the entire duration of the gaze to record 'Gaze away'. For example, if you look away for 1 second and return to the road for 1.5 seconds, you would press and hold the trigger for 1 second and let it go for 1.5 seconds.
The plugin will accumulate the time the trigger is held over the defined period and also highlight other test-specific criteria. For example, if the time to the road ahead (time of trigger off) is ≥ 2 seconds as per the specific VATS requirement.
The important measurables for this assessment are:
- t_Road
- t_Away
- Gaze Transition (t_Road-t_Away)
- T0
- Twarn (EoT condition given by the start of an Audio or Visual warning to the driver)
The run results will be shown in the Results table, including Pass/Fail, Test Duration and TAudio/TVisual, denoting the duration from the start of the test until the warning.
Chart Options
The DSM: Short Distraction plugin has a unique section on the Graph ribbon, where you can find plugin-specific tools.
Add t_Away - Add a t-Away event to the test by clicking on the Add t-Away button with the cursor at the required location in the chart.
Add t_Road - Add a t-Road event to the test by clicking on the Add t-Road button with the cursor at the required location in the chart.
| Note: When you add a t-Away or t_Road event, you must add a corresponding t-Road or t-Away event. |
When you have added one or more events to the test, the selected event will be displayed. Click on the dropdown arrow next to the event name to see the available events in the test and select a different one.
You can rename the events in the test. Select the required event and click Rename.
You can delete events from the test. Select the required event and click Delete.
Back -4s - Click on the Back -4s button to move the cursor to 4 seconds before the start-of-test point in the chart.
Toggle Metronome - Click the Toggle Metronome button to enable a click track of 120 bpm. You can use this to keep time when triggering "look away" and "look back" actions required for the test.
Toggle Line Results - The short distraction test is made from multiple on/off triggers in a single test run, so we have added the extra functionality to toggle the line results. Click on the Toggle Line Results button to show or hide the individual line data from each trigger on/off activation. This is useful for post-processing of individual line results. For example, to assess where a test was out of bounds.
Offline Test
It is up to each user to consider what is defined as an outlier for the test. Where, however, there could be a discrepancy that would benefit from offline assessment is the ‘return to road ahead’ validation. Given that this is defined as ‘test invalid if it is ≥ 2 seconds', then edge cases are possible and should be considered.
To perform the post-process assessment, you must first stop the logging on both HD2 units and remove the SD cards. The data on each SD card can be stored locally, and you can load it in a second session in Test Suite. This session must be in Offline mode, and you must load the data from both HD2 units.
| Note: You must load the file that contains the CAN data first and set the configuration to the same as the configuration in Online mode (remember that the channel names are user-defined). |
Once both HD2 files have been loaded into Test Suite, they will automatically sync and move frame-by-frame as you navigate the files.
The Results tab should show the same results as the online test, and the graph will show the exact start and end of the test (defined by the Trigger for test start and Audio/Visual trigger for test end).
You can now identify the runs (tests) that are considered edge cases in your scenario. These edge cases can then be assigned for scrutiny or further analysis
