Checklist
Description
The SafetyPool scenarios do not explicitly assign a route/goal to each entity in the scenario. This leaves the behavior of each entity up to the default controller of the scenario interpreter, which may be inconsistent. In particular, SSv2 requires the goal position for each entity to be explicitly assigned, otherwise they will not move. This task involves proposing a logic to generate a plausible goal position to each entity and assign them via RoutingAction in the converted scenario.
Purpose
To ensure that the NPCs can move in a plausible way in the SSv2 simulation.
Possible approaches
- Consider possible algorithms to select a plausible goal lane and position
- Implement the logic
- Check that a set of SafetyPool scenarios can be executed with plausible NPC behavior
Definition of done
The logic to automatically assign routes/goals to the scenario entities is implemented and verified against a set of SafetyPool scenarios
Checklist
Description
The SafetyPool scenarios do not explicitly assign a route/goal to each entity in the scenario. This leaves the behavior of each entity up to the default controller of the scenario interpreter, which may be inconsistent. In particular, SSv2 requires the goal position for each entity to be explicitly assigned, otherwise they will not move. This task involves proposing a logic to generate a plausible goal position to each entity and assign them via RoutingAction in the converted scenario.
Purpose
To ensure that the NPCs can move in a plausible way in the SSv2 simulation.
Possible approaches
Definition of done
The logic to automatically assign routes/goals to the scenario entities is implemented and verified against a set of SafetyPool scenarios