1. Driving Simulator Performance Variables: An Overview Ronald R. Mourant – Northeastern University – mourant@coe.neu.edu

2. Possible Dependent Variables For Driving Scenarios Vehicle path profiles Vehicle velocity profile Heart rate and / or GSR Driver search and scan patterns Number of collisions or incidents Time to take evasive / protective action activate brake activate accelerator turn the steering wheel

3. Recording a Vehicle's Path

4. Scenario: Lane Change into Gap

5. Factors to be Analyzed Lane deviation Steering angle deviation Eye glances (number & duration) to left-side & center mirrors during 3 periods for each scenario: 1. Pre-lane change - begins with the command to make a lane change 2. During lane change 3. Post-lane change - ends 4 seconds after vehicle is in the desired lane

6. Time: X-Coordinates & Mirror Sampling Plot - Lane Change into Gap After First Lane-Change Beep, For One Experienced Driver

8. Performance Measures for Scenarios Time (s): Elapsed time since the start of the run in seconds. X Position (ft): Driver position in the X axis in feet. Y Position (ft): Driver position in the Y axis in feet. Distdriven (miles): Distance driven since the start of the run, in miles. SpeedCar (mph): Speed of the vehicle in miles per hour. Acceleration (mph/s): Acceleration of the vehicle in mph/s; deceleration will be negative. Gas: Gas pedal value in units returned by the hardware. Brake: Brake pedal value in units returned by the hardware.

9. Performance Measures for Scenarios StrAng (deg): Angle turned by the steering wheel from the original position in degrees. StrVel (deg/s): Angular velocity of the steering wheel in degrees per second. TrackerYaw (deg): Head turn angle as measured by the head tracker, in degrees. Crashed?: If there was a crash, prints 1, otherwise 0. StopLineCrossed: Prints out the stop line’s start and end points if it were crossed between this time stamp and the previous. DistToCenterLine (ft): Distance to the centerline from the driver position is output in feet. Intersections and areas that do not have a visible centerline, have an imaginary centerline that smoothly connects the centerlines of its adjacent road segments in the direction of travel. For example if we were to make a turn, the centerline of an intersection will be a curve, and if the requirement was to go straight at an intersection, that centerline would be a straight. TileId+RoadId: This variable acts as a cross reference to the XML file and also will be useful in identifying a certain section of the run for analysis depending on the TileId and RoadId.

15. Bicycle Distraction Scenario Implemented at Northeastern University mourant@coe.neu.edu