DaD - Distracted and Drowsy - Revision history

Alexandra at 13:19, 24 July 2020

2020-07-24T13:19:41Z

Abilotti at 23:01, 9 July 2020

2020-07-09T23:01:03Z

Abilotti at 23:00, 9 July 2020

2020-07-09T23:00:46Z

Abilotti at 22:54, 9 July 2020

2020-07-09T22:54:26Z

Abilotti: Created page with "Idrive™ inside camera AI is processing images directly on-device, without any cloud connectivity or additional hardware add-ons. Idrive™ inside camera AI is running at 4 F..."

2020-07-09T21:56:39Z

Created page with "Idrive™ inside camera AI is processing images directly on-device, without any cloud connectivity or additional hardware add-ons. Idrive™ inside camera AI is running at 4 F..."

New page

Idrive™ inside camera AI is processing images directly on-device, without any cloud connectivity or additional hardware add-ons. Idrive™ inside camera AI is running at 4 FPS and at 2 FPS if also Outside Camera AI features are activated). This is done by using the optimum speed/accuracy state of the art Convolution Neural Network architectures.
Our high accuracy of 96% during the day and 91% during the night condition is obtained using a huge number of training data that we stored during the 10 years we were present in the market. Beside the quantity, a very important factor is diversity, our algorithm training data presents diversity in vehicle types, luminosity conditions, camera positioning in the car, road type and weather condition.
Distraction and Drowsiness (DaD) triggers an event called “Fatigue/Distracted”. The event is uploaded on Cloud on cellular data by default.
The DaD algorithm is searching for the driver in a specifically position set by the "driving side" parameter (IRIS->Fleet Manager-> Vehicles). Left driving side is considered the default, for any other driving position please adjust this parameter accordingly.

[[File:Driving_side.png]]

A DaD trigger is made when the driver is staying distracted more than 25% of the time in the last 6 seconds. A distraction position is considered when the driver is looking down. The driver is allowed to look lateral, in the mirrors or behind when he backs off without consider it as a distracted behavior
In order to trigger a DaD event, the vehicle must have at least 5 km/h (3.1 mph). In the areas without GPS signal like parking lots, passages, some specifically areas, etc. where we cannot estimate the car speed, if there is no GPS signal more than 90% of the time the last minute, we do not take in consideration the speed anymore until you have a GPS signal again, so will trigger a DaD event every time the driver will look down more than 25% of the last 6 seconds. On a client demands we can adjust the settings so when is no GPS signal, the camera will no trigger a DaD event (useful for clients which spends a lot of time in the parking lot without GPS signal and do not want DaD triggers). Please address engineering when is the case to make the change.
Other parameters that can be adjusted by engineering on clients/support request are:
 The default 6 seconds analyze time
 The default 25% time needed to stay distracted in order to give a DaD trigger
 Minimum speed (default: 5 km/h (3.1 miles)) that a driver should have to trigger a DaD event
 A confidence threshold which is evaluating when the driver is distracted or not (in case of too many or too few DaD events)
Please inform engineering if a client has too many false DaD events and also if no DaD are triggered when it should supposed to.
Technical recommendation
For improved accuracy mount the camera as closest to the drivers face on both horizonal and vertical axis

← Older revision		Revision as of 13:19, 24 July 2020
Line 28:		Line 28:


−	'''A DaD trigger is made when the driver is distracted more than 25% of the time in the last 6 seconds'''	+	'''A DaD trigger is made when the driver is distracted more than 35% of the time in the last 6 seconds'''

	A distracted position is considered when the driver is looking down		A distracted position is considered when the driver is looking down

← Older revision		Revision as of 23:01, 9 July 2020
Line 60:		Line 60:

	'''NOTE:''' Please inform engineering if a client has too many false DaD events and also if no DaD are triggered when it should supposed to.		'''NOTE:''' Please inform engineering if a client has too many false DaD events and also if no DaD are triggered when it should supposed to.
−
−

@@ Line 46: / Line 46: @@
-On a client demands we can adjust the settings so when is no GPS signal, the camera will no trigger a DaD event (useful for clients which spends a lot of time in the parking lot without GPS signal and do not want DaD triggers). Please address engineering when is the case to make the change.
+Upon client demands we can adjust the settings so during times of no GPS signal, the camera will no trigger a DaD event
-	Other parameters that can be adjusted by engineering on clients/support request are:
+::- useful for clients which spend a lot of time in the covered parking garages without GPS signal and do not want DaD triggers during those times
-	The default 6 seconds analyze time
+::::- Please address engineering when this is the case to make the change
-	The default 25% time needed to stay distracted in order to give a DaD trigger
-	Minimum speed (default: 5 km/h (3.1 miles)) that a driver should have to trigger a DaD event
-	A confidence threshold which is evaluating when the driver is distracted or not (in case of too many or too few DaD events)
-Please inform engineering if a client has too many false DaD events and also if no DaD are triggered when it should supposed to.
+Other parameters that can be adjusted by engineering upon client/ Idrive Support request are:
-Technical recommendation
+*The default 6 seconds analyze time
-For improved accuracy mount the camera as closest to the drivers face on both horizonal and vertical axis
+*The default 25% time needed to stay distracted in order to give a DaD trigger

@@ Line 1: / Line 1: @@
-Idrive™ inside camera AI is processing images directly on-device, without any cloud connectivity or additional hardware add-ons. Idrive™ inside camera AI is running at 4 FPS and at 2 FPS if also Outside Camera AI features are activated). This is done by using the optimum speed/accuracy state of the art Convolution Neural Network architectures.
+Idrive™ inside camera AI is processing images directly the on-device without any cloud connectivity or additional hardware add-ons.
-Our high accuracy of 96% during the day and 91% during the night condition is obtained using a huge number of training data that we stored during the 10 years we were present in the market. Beside the quantity, a very important factor is diversity, our algorithm training data presents diversity in vehicle types, luminosity conditions, camera positioning in the car, road type and weather condition.
-Distraction and Drowsiness (DaD) triggers an event called “Fatigue/Distracted”. The event is uploaded on Cloud on cellular data by default.
+Idrive™ inside camera AI is running at 4 FPS and at 2 FPS if Outside Camera AI features are activated.
-The DaD algorithm is searching for the driver in a specifically position set by the "driving side" parameter (IRIS->Fleet Manager-> Vehicles). Left driving side is considered the default, for any other driving position please adjust this parameter accordingly.
+:- This is done by using the optimum speed/accuracy state of the art Convolution Neural Network (CNN) architectures.
 [[File:Driving_side.png]]
@@ Line 8: / Line 28: @@
-A DaD trigger is made when the driver is staying distracted more than 25% of the time in the last 6 seconds. A distraction position is considered when the driver is looking down. The driver is allowed to look lateral, in the mirrors or behind when he backs off without consider it as a distracted behavior
+'''A DaD trigger is made when the driver is distracted more than 25% of the time in the last 6 seconds'''
-	In order to trigger a DaD event, the vehicle must have at least 5 km/h (3.1 mph). In the areas without GPS signal like parking lots, passages, some specifically areas, etc. where we cannot estimate the car speed, if there is no GPS signal more than 90% of the time the last minute, we do not take in consideration the speed anymore until you have a GPS signal again, so will trigger a DaD event every time the driver will look down more than 25% of the last 6 seconds. On a client demands we can adjust the settings so when is no GPS signal, the camera will no trigger a DaD event (useful for clients which spends a lot of time in the parking lot without GPS signal and do not want DaD triggers). Please address engineering when is the case to make the change.
 	Other parameters that can be adjusted by engineering on clients/support request are:
 	The default 6 seconds analyze time