Configuring ADAS Library Parent topic: Configuring ADAS Library

Input

Inputs are defined in a single array named input in JSON format.

Specifying inputs is mandatory. You must specify the input array in your configuration file with at least one entry. For example: 

...
    "input": [
        {
            "source": "sensor",            
            "instance": "SENSOR_UNIT_1",
            "id": "forward_camera",
            "record": {
                "format": "MP4",
            },
        },
        {
            "source": "sensor",            
            "name": "vlp-16",
            "id": "front_lidar",
            "record": {
                "format": "MP4",
            },
        },
        ...
     ]
...

Attributes:

There are the attributes that you can use to configure an input.

id
(Required) An identifier that can be used to distinguish this input in the context of this ADAS library configuration file. The string must be unique among the array of inputs.
instance
(Optional) The instance of an input. This should correspond to the sensor unit that's in the sensor configuration file (e.g. SENSOR_UNIT_1). For examples of valid entries for instance, see ../../../com.qnx.doc.adas.system_services/topic/sensor_service_configuration_file.html. If not specified, the ADAS library ignores the sensor unit associated with the input.
name
(Optional) The string from the sensor or data configuration file that's associated with this input. The name must be identical to that specified in the name parameter of the corresponding sensor that's in the sensor or data configuration file.
orientation
(Optional) The orientation of the sensor as specified by the direction parameter of the corresponding sensor in the sensor or data configuration file. Valid entries for this attribute are:
  • back
  • front
  • left
  • right
If not specified, the ADAS library ignores the orientation of the sensor.
record
(Optional) The configuration used for recordings. The record attribute is defined by the following data:
  • format

    The format in which you want to record this sensor. Valid entries for format are:

    • UCV (default for cameras): a proprietary uncompressed video file format (valid for all formats of cameras)
    • MP4: an H.264 video that's recorded in an MP4 file format
    • MOV: an uncompressed video in a QuickTime MOV file format (valid for only spcific formats of cameras)
    • RAW: a proprietary uncompressed recording of sensor data
    • GZIP: a GZIP-compressed file containing sensor data
    • LZ4 (default for sensors): an LZ4-compressed file containing sensor data
  • directory

    The path to a directory for your recording. Specify roll (the default if you don't specify directory) to use the roll directory that's specified at the start of the Sensor service.

  • filename

    The filename for your recording. Specify roll (the default if you don't specify to filename) to use a unique filename from the directory that's specified at the start of the Sensor service.

For example: 
...
            "record": {
                "format": "MP4",
                "directory": "roll",
                "filename": "roll"
            },
...
source
(Required) The identifier that indicates whether or not this input is a sensor or interim data. Valid entries for this attribute are:
  • sensor — a physical sensor that's in the sensor configuration file
  • interim_data — an sensor unit that corresponds to interim data that's in the data configuration file
type
(Optional) The type of sensor. Valid entries for this attribute are:
  • camera
  • gps
  • imu
  • lidar3D (e.g., a Velodyne lidar that generates a point cloud)
  • lidar2D (e.g., a Leddartech lidar that generates only a few points)
  • radar
If not specified, the ADAS library ignores the sensor type.
Parent topic: Configuring ADAS Library