Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: added rviz_config to the launch script #606

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,8 @@
record:=false \
scenario:='/path/to/scenario/sample.yaml' \
sensor_model:=sample_sensor_kit \
vehicle_model:=sample_vehicle
vehicle_model:=sample_vehicle \
rviz_config:=$($(ros2 pkg prefix autoware_launch)/share/autoware_launch/rviz/scenario_simulator.rviz)
```

- Now, the scenario will be executed in the Scenario Simulator. You can see the simulation in the RViz window.
Expand All @@ -190,7 +191,7 @@
- Firstly, you should create a free TIER IV account to access the Autoware Evaluator. You can create an account by using
the [TIER IV account creation page](https://account.tier4.jp/registration).

- After you created an account, please reach out to Hiroshi IGATA (hiroshi.igata@tier4.jp), the AWF ODD WG leader, for

Check warning on line 194 in docs/how-to-guides/others/planning-evaluation-using-scenarios.md

View workflow job for this annotation

GitHub Actions / spell-check-differential

Unknown word (Hiroshi)

Check warning on line 194 in docs/how-to-guides/others/planning-evaluation-using-scenarios.md

View workflow job for this annotation

GitHub Actions / spell-check-differential

Unknown word (IGATA)
an invitation to AWF project of the Autoware Evaluator. It is advised to join the ODD WG meeting once to briefly
introduce yourself and your interest. The ODD WG information
is [here](https://github.com/autowarefoundation/autoware-projects/wiki/operational-design-domain-working-group#how-to-participate-in-the-working-group).
Expand Down Expand Up @@ -260,7 +261,7 @@

This page show us the detailed information of the failed case. We can understand why the case failing by looking into
the `Message`. For our case, the message
is `Simulation failure: CustomCommandAction typed "exitFailure" was triggered by the anonymous Condition (OpenSCENARIO.Storyboard.Story[0].Act["_EndCondition"].ManeuverGroup[0].Maneuver[0].Event[1].StartTrigger.ConditionGroup[1].Condition[0]): The state of StoryboardElement "act_ego_nostop_check" (= completeState) is given state completeState?`

Check warning on line 264 in docs/how-to-guides/others/planning-evaluation-using-scenarios.md

View workflow job for this annotation

GitHub Actions / spell-check-differential

Unknown word (nostop)

From this message, we can understand that an action which is used for checking the vehicle is not stopped is in complete
state. And, the scenario author set this condition as a failure condition. Therefore, the scenario failed.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,8 @@
record:=false \
scenario:='$(find-pkg-share scenario_test_runner)/scenario/sample.yaml' \
sensor_model:=sample_sensor_kit \
vehicle_model:=sample_vehicle
vehicle_model:=sample_vehicle \
rviz_config:=$($(ros2 pkg prefix autoware_launch)/share/autoware_launch/rviz/scenario_simulator.rviz)
```

![scenario_test_runner](images/scenario_test_runner.png)
Expand Down
Loading