|
|
Scenarios can be entirely defined using a single JSON file.
|
|
|
This approach is more verbose than the *SimLand* and *CarLang* approach but is easier to implement in the simulator and is thus easier to keep up-to-date.
|
|
|
|
|
|
## Reference Tables
|
|
|
|
|
|
The following pages contain tables describing all the entries for scenarios.
|
|
|
The root entry in the JSON scenario file must be the `SimulationConfig` entry.
|
|
|
|
|
|
- [Simulation Configuration](/user-docs/json-scenario-reference/Simulation-Configuration)
|
|
|
- [Vehicle Configuration](/user-docs/json-scenario-reference/Vehicle-Configuration)
|
|
|
- [TaskProperties](/user-docs/json-scenario-reference/TaskProperties)
|
|
|
- [Body and Wheel Properties](/user-docs/json-scenario-reference/Body-and-Wheel-Properties)
|
|
|
- [PowerTrainProperties](/user-docs/json-scenario-reference/PowerTrainProperties)
|
|
|
- [BusProperties](/user-docs/json-scenario-reference/BusProperties) (*Buses*)
|
|
|
- [Sensor and Actuator Properties](/user-docs/json-scenario-reference/Sensor-and-Actuator-Properties) (*EE-components*)
|
|
|
- [Bridge, Navigation and SimpleCommunicationGateway Properties](/user-docs/json-scenario-reference/Bridge,-Navigation-and-SimpleCommunicationGateway-Properties) (*EE-components*)
|
|
|
- [TestAutopilot and JavaAutopilot Properties](/user-docs/json-scenario-reference/TestAutopilot-and-JavaAutopilot-Properties) (*EE-components*)
|
|
|
- [ComputerProperties](/user-docs/json-scenario-reference/ComputerProperties) (*EE-component*)
|
|
|
|
|
|
### Defaults
|
|
|
|
|
|
The last column in the tables can show a default value for an entry.
|
|
|
When one is defined in the table, the scenario file can omit the entry and the default value will be used.
|
|
|
|
|
|
### Typed entries
|
|
|
|
|
|
Some entries in the scenarios have sub-types (for example instances of the `EEComponent` properties).
|
|
|
These object entries must always contain the `"type": "..."` entry as **first entry**.
|
|
|
|
|
|
## Symbols Used
|
|
|
|
|
|
These are used in the following config specification tables.
|
|
|
|
|
|
### Types
|
|
|
|
|
|
The *Type* columns in the tables specify the JSON type to use in order to describe the property.
|
|
|
|
|
|
| Type | Meaning |
|
|
|
| :--- | :------ |
|
|
|
| FP | Floating Point / Decimal Number |
|
|
|
| I | Integer Number |
|
|
|
| S | String |
|
|
|
| O | Object |
|
|
|
| [S] | List of Strings |
|
|
|
| [O] | List of Objects |
|
|
|
| Duration | Specified as `[secs, nanosecs]` |
|
|
|
| Instant | Specified as `[epoch_secs, nanosecs]` |
|
|
|
|
|
|
### Units
|
|
|
|
|
|
Specifies how the values are interpreted in the simulation.
|
|
|
|
|
|
| Unit | Meaning |
|
|
|
| :--- | :------ |
|
|
|
| kg | Kilogram |
|
|
|
| m | Meter |
|
|
|
| cm | Centimeter |
|
|
|
| deg | Degrees |
|
|
|
| N | Newtons |
|
|
|
| J | Joules |
|
|
|
|
|
|
---
|
|
|
Next: [Simulation Configuration](/user-docs/json-scenario-reference/Simulation-Configuration) |
|
|
\ No newline at end of file |