Skip to content

Commit 1904b2a

Browse files
committed
chore: Update Longitudinal_control.md with additional details for requestSpeedChange API
1 parent 935d1f4 commit 1904b2a

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

docs/developer_guide/Longitudinal_control.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,12 +50,14 @@ If `continuous` is set to `false`, job to accelerate to target speed will be del
5050
When `constraint` is set to `LONGITUDINAL_ACCELERATION`, the entity will accelerate to the target speed with acceleration rate you set.
5151
- If `transition` is set to `LINEAR`, the entity will accelerate to the target speed linearly.
5252
- If `transition` is set to `AUTO`, it will change the maximum acceleration speed of the entity and append the job to change the target speed of the npc to the job queue. After the npc reaches the target speed, it will change the maximum acceleration speed back to the original value.
53-
- If `transition` is set to `STEP`, it
53+
- If `transition` is set to `STEP`, it will
5454

5555

5656
When `constraint` is set to `TIME`, the entity will accelerate to the target speed by the time you set.
5757
When `constraint` is set to `NONE`, is will append the job to change the target_speed of the npc to the job queue.
5858

59+
`change target speed` block in the below figure is the highest priority compared to other blocks.
60+
If target speed is set somewhere else, the entity will try to change the speed to the target speed under acceleration/deceleration constraints set by the user or if not by the default value.
5961
![requestSpeedChange](../images/Longitudinal_control/requestSpeedChange.png)
6062

6163

27.5 KB
Loading

0 commit comments

Comments
 (0)