... | ... | @@ -128,7 +128,7 @@ An `Agent` element describes a single agent in the simulation. It has the follow |
|
|
| `remove_at_goal` | No | Boolean | Whether or not the agent should be removed from the simulation when it has reached its goal position. | `false` |
|
|
|
| `start_time` | No | float, >= 0 | The time (in seconds since the start of the simulation) after which the agent should be added. This allows you to insert agents over time. | 0 |
|
|
|
|
|
|
**Warning:** If an attribute or element is missing from the XML file, it will be replaced by a default value from this table if possible. After this replacement step, if any value is incorrect (such as a negative agent radius), the agent will not be added to the simulation.
|
|
|
**Warning:** If an attribute is missing from the XML file, it will be replaced by a default value from this table if possible. After this replacement step, if any value is incorrect (such as a negative agent radius), the agent will not be added to the simulation.
|
|
|
|
|
|
An `Agent` element has the following **child elements**:
|
|
|
|
... | ... | @@ -169,7 +169,7 @@ In line with the I3D 2020 publication, a policy has two main ingredients: |
|
|
- one or more *cost functions* that assign a cost to the possible velocities that an agent can use,
|
|
|
- an *optimization method* that describes how to use these cost functions in the simulation.
|
|
|
|
|
|
In XML, cost functions are specified as child elements, and the optimization method is specified via attributes.
|
|
|
In XML, cost functions are specified via one or more **child elements** named `CostFunction`. We will treat the `CostFunction` element in a separate section. The optimization method is specified via attributes, along with all other relevant parameters.
|
|
|
|
|
|
A `Policy` element has the following **main attributes**:
|
|
|
|
... | ... | @@ -193,3 +193,7 @@ Furthermore, a `Policy` element has the following **extra attributes** related t |
|
|
| `AngleSamples` | No | int, > 0 | **(See the image below)** The number of different angles to use for regular sampling. Only used if `OptimizationMethod="sampling"` *and* `Type="regular"`. | 11 |
|
|
|
| `IncludeBaseAsSample` | No | Boolean | **(See the image below)** Whether or not to always include the base velocity for regular sampling. This also affects the distance between speed samples. Only used if `OptimizationMethod="sampling"` *and* `Type="regular"`. | `false` |
|
|
|
| `RandomSamples` | No | int, > 0 | The number of random sample velocities to test. Only used if `OptimizationMethod="sampling"` *and* `Type="random"`. | 100 |
|
|
|
|
|
|
**Warning:** If an attribute is missing from the XML file, it will be replaced by a default value from this table if possible. After this replacement step, if any value is incorrect (such as a negative sampling angle), the policy will not be loaded, and therefore the simulation cannot start.
|
|
|
|
|
|
### 'CostFunction' element |