Scenario Planner

Node ID: scenarioPlanner · Role: Sink · Realtime config: no

Description

Scenario planner sink, which communicates with the renderer. Takes a vehicle pose which is used to drive the activations and car position in the scenario. Optionally can also drive additional objects in the scene with FusedPoses from vehicle or IMU-Optical fusion.

Inputs / Outputs

• Inputs: car (FusedPose) - FusedPose - Main Vehicle - /car
• Outputs: (none)

Config aliases

ScenarioPlanner, scenarioPlanner

Properties

Each row shows the setting’s label in the node’s Properties panel and, in code, its key in the node’s settings object in the config file. A setting omitted from the config file uses the default shown here.

Example node definition

A minimal entry in config.json looks like the block below. Paste it under the sinks key, keyed by an instance name of your choice. All settings are optional: anything not listed under settings uses the default from the Properties table above. See The configuration file for how the sections and endpoint wiring work.

{
  "sinks": {
    "scenarioPlanner": {
      "inputEndpoints": [
        "inproc://car_data"
      ],
      "inputDataFilter": [
        "FusedPose"
      ],
      "settings": {}
    }
  }
}