-
Notifications
You must be signed in to change notification settings - Fork 61
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1421 from tier4/feature/manual_on_follow_trajecto…
…ry_with_new_state
- Loading branch information
Showing
15 changed files
with
401 additions
and
52 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
40 changes: 40 additions & 0 deletions
40
docs/developer_guide/ManualOverrideWithFollowTrajectoryAction.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
# Manual Override Simulation with FollowTrajectoryAction | ||
|
||
`scenario_simulator_v2` simulates the manual override of Autoware, with `FollowTrajectoryAction`. | ||
During the executing `FollowTrajectoryAction`, the control of the ego entity is taken over from Autoware to the `FollowTrajectoryAction`. | ||
|
||
## 3 types of override for Autoware | ||
|
||
There are 3 types of override for Autoware. | ||
|
||
- Local: Manually control the vehicle from nearby with some device such as a joystick. | ||
- This is one of operation modes. | ||
- Remote: Manually control the vehicle from a web application on the cloud. | ||
- This is one of operation modes. | ||
- Direct: Manually control the vehicle from handle, brake and/or accel directly. | ||
- Please note that this is not a operation mode but a control mode of vehicle interface. | ||
|
||
## override simulation in scenario_simulator_v2 | ||
|
||
vehicle interface simulation is a part of the ego vehicle simulation feature in `scenario_simulator_v2`. | ||
`scenario_simulator_v2` simulates a `Direct` override triggered by safety operators when a scenario commands overriding the ego vehicle by `FollowTrajectoryAction`. | ||
|
||
## 3 steps scenario_simulator_v2 takes to simulate the overrides | ||
|
||
### 1. triggering the override | ||
|
||
In real vehicle, the override detected in vehicle internally and communicated to vehicle interface node such as `pacmod_interface` node. | ||
|
||
In `scenario_simulator_v2`, `openscenario_interpreter` send an override flag via zmq interface between `traffic_simulator` and `simple_sensor_simulator` when `FollowTrajectoryAction` is started. | ||
|
||
`simple_sensor_simulator` receives it and set the control mode to MANUAL like vehicle interface do when hardware override triggers detected. | ||
|
||
### 2. during the override | ||
|
||
`traffic_simulator` send ego status calculated to follow described in the scenario and `simple_sensor_simulator` overrides Autoware control with overwriting ego status by the received ego status. | ||
|
||
### 3. finishing the override | ||
|
||
When `FollowTrajectoryAction` is finished, `traffic_simulator` call service to enable autoware control and stop sending the override flag to `simple_sensor_simulator` via zmq communication. | ||
|
||
This mimics the steps safety operators do in real vehicle via some human interfaces, in API level. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.