Skip to content

Commit

Permalink
docs(autoware_autonomous_emergency_braking): improve AEB module's REA…
Browse files Browse the repository at this point in the history
…DME (autowarefoundation#8612)

* docs: improve AEB module's README

Signed-off-by: Kyoichi Sugahara <kyoichi.sugahara@tier4.jp>

* update rss distance length

Signed-off-by: Kyoichi Sugahara <kyoichi.sugahara@tier4.jp>
---------

Signed-off-by: Kyoichi Sugahara <kyoichi.sugahara@tier4.jp>
  • Loading branch information
kyoichi-sugahara authored and danielsanchezaran committed Oct 28, 2024
1 parent ca47de3 commit de5da9b
Show file tree
Hide file tree
Showing 2 changed files with 65 additions and 126 deletions.
8 changes: 4 additions & 4 deletions control/autoware_autonomous_emergency_braking/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,6 @@

This module has following assumptions.

- It is used when driving at low speeds (about 15 km/h).

- The predicted path of the ego vehicle can be made from either the path created from sensors or the path created from a control module, or both.

- The current speed and angular velocity can be obtained from the sensors of the ego vehicle, and it uses points as obstacles.
Expand All @@ -25,7 +23,7 @@ The pros and cons of both approaches are:
IMU angular velocity:

- (+) Usually, it has high accuracy
- (-)Vehicle vibration might introduce noise.
- (-) Vehicle vibration might introduce noise.

Steering angle:

Expand Down Expand Up @@ -186,7 +184,7 @@ The AEB module can also prevent collisions when the ego vehicle is moving backwa

When vehicle odometry information is faulty, it is possible that the MPC fails to predict a correct path for the ego vehicle. If the MPC predicted path is wrong, collision avoidance will not work as intended on the planning modules. However, the AEB’s IMU path does not depend on the MPC and could be able to predict a collision when the other modules cannot. As an example you can see a figure of a hypothetical case in which the MPC path is wrong and only the AEB’s IMU path detects a collision.

![backward driving](./image/wrong-mpc.drawio.svg)
![wrong mpc](./image/wrong-mpc.drawio.svg)

## Parameters

Expand Down Expand Up @@ -217,6 +215,8 @@ When vehicle odometry information is faulty, it is possible that the MPC fails t

## Limitations

- The distance required to stop after collision detection depends on the ego vehicle's speed and deceleration performance. To avoid collisions, it's necessary to increase the detection distance and set a higher deceleration rate. However, this creates a trade-off as it may also increase the number of unnecessary activations. Therefore, it's essential to consider what role this module should play and adjust the parameters accordingly.

- AEB might not be able to react with obstacles that are close to the ground. It depends on the performance of the pre-processing methods applied to the point cloud.

- Longitudinal acceleration information obtained from sensors is not used due to the high amount of noise.
Expand Down
Loading

0 comments on commit de5da9b

Please sign in to comment.