You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Traffic Light Simulation | Start supporting to traffic light messages in `autoware_perception_msgs`. |`openscenario_interpreter`, `traffic_simulator`, `simple_sensor_simulator`|[#1027](https://github.com/tier4/scenario_simulator_v2/pull/1027)|[HansRobo](https://github.com/HansRobo)|
10
-
| Detailed control of permissions for autonomous decisions | Add `featureIdentifiersRequiringExternalPermissionForAutonomousDecisions` property for ObjectController. scenario_simulator_v2 controls auto_mode of Autoware planning modules by settings in the property. |`openscenario_interpreter`, `concealer`|[#1092](https://github.com/tier4/scenario_simulator_v2/pull/1092)|[HansRobo](https://github.com/HansRobo)|
11
-
| OpenSCENARIO `Controller.Properties.Property`| Support the property `allowGoalModification` to turn on the Autoware feature `allow_goal_modification`. |`openscenario_interpreter`, `concealer`|[#997](https://github.com/tier4/scenario_simulator_v2/pull/997)|[yamacir-kit](https://github.com/yamacir-kit)|
12
-
| OpenSCENARIO 1.2 `UserDefinedAction.CustomCommandAction`| Add `PseudoTrafficSignalDetectorConfidenceSetAction@v1`, a CustomCommandAction to control confidences in traffic light topic. |`openscenario_interpreter`, `traffic_simulator`|[#1111](https://github.com/tier4/scenario_simulator_v2/pull/1111)|[HansRobo](https://github.com/HansRobo)|
| Add `API::getLaneletLength()` and `API::getMapPoseFromRelativePose()`| Add `API::getLaneletLength()`to get a length of target lanelet, and `API::getMapPoseFromRelativePose()` to transform relative pose to map pose. |`traffic_simulator`|[#1145](https://github.com/tier4/scenario_simulator_v2/pull/1145)|[hakuturu583](https://github.com/hakuturu583)|
15
-
| Start supporting ego entity in C++ scenario | Enable spawn ego entity in C++ scenarios in cpp_mock_scenarios package. |`cpp_mock_scenarios`|[#1145](https://github.com/tier4/scenario_simulator_v2/pull/1145)|[hakuturu583](https://github.com/hakuturu583)|
| Traffic Light Simulation | Start supporting to traffic light messages in `autoware_perception_msgs`. |`openscenario_interpreter`, `traffic_simulator`, `simple_sensor_simulator`|[#1027](https://github.com/tier4/scenario_simulator_v2/pull/1027)|[HansRobo](https://github.com/HansRobo)|
10
+
| Detailed control of permissions for autonomous decisions | Add `featureIdentifiersRequiringExternalPermissionForAutonomousDecisions` property for ObjectController. scenario_simulator_v2 controls auto_mode of Autoware planning modules by settings in the property. |`openscenario_interpreter`, `concealer`|[#1092](https://github.com/tier4/scenario_simulator_v2/pull/1092)|[HansRobo](https://github.com/HansRobo)|
11
+
| OpenSCENARIO `Controller.Properties.Property`| Support the property `allowGoalModification` to turn on the Autoware feature `allow_goal_modification`. |`openscenario_interpreter`, `concealer`|[#997](https://github.com/tier4/scenario_simulator_v2/pull/997)|[yamacir-kit](https://github.com/yamacir-kit)|
12
+
| OpenSCENARIO 1.2 `UserDefinedAction.CustomCommandAction`| Add `PseudoTrafficSignalDetectorConfidenceSetAction@v1`, a CustomCommandAction to control confidences in traffic light topic. |`openscenario_interpreter`, `traffic_simulator`|[#1111](https://github.com/tier4/scenario_simulator_v2/pull/1111)|[HansRobo](https://github.com/HansRobo)|
| Add `API::getLaneletLength()` and `API::getMapPoseFromRelativePose()`| Add `API::getLaneletLength()`to get a length of target lanelet, and `API::getMapPoseFromRelativePose()` to transform relative pose to map pose. |`traffic_simulator`|[#1145](https://github.com/tier4/scenario_simulator_v2/pull/1145)|[hakuturu583](https://github.com/hakuturu583)|
15
+
| Start supporting ego entity in C++ scenario | Enable spawn ego entity in C++ scenarios in cpp_mock_scenarios package. |`cpp_mock_scenarios`|[#1145](https://github.com/tier4/scenario_simulator_v2/pull/1145)|[hakuturu583](https://github.com/hakuturu583)|
16
+
| Visualize context in rviz display | Enable visualize `openscenario_interpreter_msgs/msg/Context` messages in rviz display |`openscenario_visualization`|[#1033](https://github.com/tier4/scenario_simulator_v2/pull/1033)|[kyoichi-sugahara](https://github.com/kyoichi-sugahara)|
# **Visualizing the Internal Information of the Simulator**
2
+
3
+
This document provides instructions for users on how to visualize the internal information of `scenario_simulator_v2` using rviz. It also covers features that can be beneficial for analyzing this information. Please note, **this document is based on information up to version v0.7.0**.
4
+
5
+
## Table of Contents
6
+
7
+
-[**Visualizing the Internal Information of the Simulator**](#visualizing-the-internal-information-of-the-simulator)
-[**Visualizing the Status of ConditionGroups**](#visualizing-the-status-of-conditiongroups)
11
+
12
+
## **Visualizing Entity Information**
13
+
14
+
WIP
15
+
16
+
## **Visualizing the Status of ConditionGroups**
17
+
18
+
`ConditionGroup`s defined in the scenario file can be checked on rviz, a visualization tool.
19
+
20
+
A `ConditionGroup` acts as a trigger for events described in the scenario. A `ConditionGroup` is deemed true when all its sub-Conditions are fulfilled. Furthermore, event triggers can have multiple `ConditionGroup`s. If the evaluation of any one `ConditionGroup` becomes true, the trigger is activated.
21
+
22
+
One usage example is to display `ConditionGroup`s at the moment the scenario fails. This allows you to analyze the cause of the failure.
23
+
24
+
The display structure is as follows, and allows multiple Conditions to be included in one `ConditionGroup`:
25
+
26
+
```markdown
27
+
Condition Group Name: xxx
28
+
Current Evaluation: xxx
29
+
Current Value: true/false
30
+
Type: ReachPositionCondition, CollisionCondition, etc.
31
+
Current Evaluation:
32
+
Current Value:
33
+
Type:
34
+
︙
35
+
Condition Group Name: xxx
36
+
Current Evaluation: xxx
37
+
Current Value: true/false
38
+
Type: ReachPositionCondition, CollisionCondition, etc.
39
+
Current Evaluation:
40
+
Current Value:
41
+
Type:
42
+
︙
43
+
```
44
+
45
+
Each condition is described using three elements:
46
+
47
+
-**Current Evaluation**: Current achievement status
48
+
-**Current Value**: The fulfillment status of the condition expressed in true/false
49
+
-**Type**: Types of conditions, such as `ReachPositionCondition`, `CollisionCondition`, etc.
50
+
51
+
To visualize the achievement status, check the `ConditionGroup` checkbox as demonstrated in the image below.
52
+
")
53
+
54
+
If an `Event name` is defined in the `ConditionGroup`, that name will be reflected. If left blank, names like `ConditionGroup1`, `ConditionGroup2`, `ConditionGroup3`, etc. are automatically assigned. However, this information alone doesn't clarify if each `ConditionGroup` is linked to success or failure conditions. Therefore, when visualizing with rviz and you want this information to be apparent, we recommend explicitly defining the `Event name` as `SuccessCondition` or similar when creating the scenario file.
0 commit comments