Abrupt and aggressive speed control

[seitzseb]

Detailed Description

The agent’s speed controller is overly aggressive when accelerating from green lights, leading to abrupt starts and stops. This behavior results in uncomfortable and potentially unsafe maneuvers in traffic situations.

Definition of Done

Speed control is smoother when accelerating from a stop, with no abrupt starts and stops.
Agent accelerates and decelerates in a controlled manner in various traffic conditions.

Effort Estimate

5

Testability

Test in a variety of stop-and-go scenarios, particularly at traffic lights, to confirm smooth acceleration and deceleration without sudden jerks.

Dependencies

Depends on proper sensor data feedback and any control code revisions related to speed adjustments.

[vinzenzm]

As the changing traffic light gets recognized correctly I will remove perception label.

The issue arises because there is infinite acceleration possible with the current throttle controller.
Therefore this is primarily an acting issue. There should be less acceleration when starting from a standstill.

We could decide on also planning an acceleration pattern for specific situations. E.g. accelerate faster if Firestruck approaches from side. Accelerate slower because next traffic light is red anyway. Therefore I will add the planning label inttermittently.
Currently however the interface between acting and planning would not allow for this. This issue is therefore also related to #421 where I supposed a new Interface between acting and planning.

I therefore suppose 3 different solutions with increasing implementation effort:

1. Limit acceleration in acting routine by limiting throttle command on low speeds.
2. Implement proper trajectory planning (S-Curve profile)
   https://www.pmdcorp.com/resources/type/articles/get/mathematics-of-motion-control-profiles-article
3. Solution 2 with the addition of above mentioned interface to be able to adapt to future speed limits or more.

@seitzseb as far as I am aware of this there is no penalty in the driving score for such jerky movement.
I will therefore add label p_3 as low priority.

If we decide on not involving planning (not Solution 3) we can also remove planning label.

My personal opinion would be so see if any issues with driving performance arise from this eratic behaviour before spending to much time on it.