From 666da435cdc69a66c004d7d4589788489d4aa364 Mon Sep 17 00:00:00 2001
From: Ralf524 <ralf.bernitt@uni-a.de>
Date: Fri, 1 Nov 2024 09:53:09 +0100
Subject: [PATCH] Create Obstacle_detection.md

---
 .../paf24/perception/Obstacle_detection.md    | 56 +++++++++++++++++++
 1 file changed, 56 insertions(+)
 create mode 100644 doc/research/paf24/perception/Obstacle_detection.md

diff --git a/doc/research/paf24/perception/Obstacle_detection.md b/doc/research/paf24/perception/Obstacle_detection.md
new file mode 100644
index 00000000..c07b84d6
--- /dev/null
+++ b/doc/research/paf24/perception/Obstacle_detection.md
@@ -0,0 +1,56 @@
+# Research: Why does the car hit obstacles
+
+## Summary of current obstacle detection in perception
+
+- [Object detection](#Object-detection)
+- [Distance calculation](#Distance-calculation)
+- [Publishing of Outputs](#Publishing-of-Outputs)
+
+For more details, please refer to the current documentation.
+
+## Object detection
+
+Active sensors:
+
+- Center camera
+- LIDAR
+
+Inactive sensors:
+
+- Cameras: right, left, back
+- Radar
+
+## Distance calculation
+
+- The vision_node receives depth-images from the lidar_distance_node for the specified camera angle
+
+- According to the distance-to-objects documentation, the LIDAR sensor's 3D values are projected onto a 2D image that matches the exact dimensions of the camera image.
+Numpy formulas are used to reconstruct the depth image, with distances in meters represented as pixel values (grayscale image).
+If no distance is found in the depth image, “infinity” is returned for this bounding box.
+
+- The LIDAR sensor may flicker; a higher spin rate of the LIDAR provides fully reconstructed depth images but with lower resolution for the LIDAR points
+
+## Publishing of Outputs
+
+- Class_index
+- Min_X
+- Min_Abs_y
+
+## Dependencies of detected and hit obstacles
+
+- Are all obstacles detected? No
+- Does successful object detection depend on:
+  - Speed of the car?
+  - Size of obstacles?
+  - Type of obstacle?
+  - Dynamic/static obstacle?
+
+-> So far, no dependencies have been found
+
+## Important aspects found during research
+
+- Sometimes objects are not detected (sometimes e.g.: cyclists, construction site signs, open car doors)
+- Most objects that are hit are detected
+- Sometimes distance calculation is incorrect (distance is set to infinity just before the collision)
+- Distance in x is alway > ~0.5 (is that a problem?), sometimes distance to a collided car is greater than the distance to a parked car on the side of the road
+- Significant issues in dead-end situations: -> 1.2 seconds of reversing -> the car often immediately collides with the obstacle again