Struct SensorView¶
Defined in File osi_sensorview.proto
Struct Documentation¶
-
struct
SensorView¶ The sensor view is derived from
GroundTruthand used as input to sensor models.The sensor view information is supposed to provide input to sensor models for simulation of actual real sensors. All information regarding the environment is given with respect to the virtual sensor coordinate system specified in
SensorView::mounting_position, except for the individual physical technology-specific data, which is given with respect to the physical sensor coordinate system specified in the corresponding physical sensor’smounting_position, and theglobal_ground_truth, which is given in global coordinates.When simulating multiple distinct sensors, each sensor can consume an individual copy of the
SensorViewinterface. This allows an independent treatment of the sensors.Alternatively combined sensor models can also consume one combined
SensorView, with either combined or separateSensorDataoutputs, depending on model architecture.Public Members
-
optional InterfaceVersion osi3::SensorView::version = 1 The interface version used by the sender (simulation environment).
-
optional Timestamp osi3::SensorView::timestamp = 2 The data timestamp of the simulation environment. Zero time is arbitrary but must be identical for all messages. Zero time does not need to coincide with the UNIX epoch. Recommended is the starting time point of the simulation.
- Note
For sensor view data this timestamp coincides both with the notional simulation time the data applies to and the time it was sent (there is no inherent latency for sensor view data, as opposed to sensor data).
-
optional Identifier osi3::SensorView::sensor_id = 3 The ID of the sensor at host vehicle’s
mounting_position.This is the ID of the virtual sensor, to be used in its detected object output; it is distinct from the IDs of its physical detectors, which are used in the detected features.
-
optional MountingPosition osi3::SensorView::mounting_position = 4 The virtual mounting position of the sensor (origin and orientation of the sensor coordinate system) given in vehicle coordinates [1]. The virtual position pertains to the sensor as a whole, regardless of the actual position of individual physical detectors, and governs the sensor-relative coordinates in detected objects of the sensor as a whole. Individual features detected by individual physical detectors are governed by the actual physical mounting positions of the detectors, as indicated in the technology-specific sub-views and sub-view configurations.
x-direction of sensor coordinate system: sensor viewing direction
z-direction of sensor coordinate system: sensor (up)
y-direction of sensor coordinate system: perpendicular to x and z right hand system
- References:
[1] DIN ISO 8855:2013-11
- Note
This field is usually static during the simulation.
- Note
The origin of vehicle’s coordinate system in world frame is (
MovingObject::base.BaseMoving::position+ Inverse_Rotation_yaw_pitch_roll(MovingObject::base.BaseMoving::orientation) *MovingObject::VehicleAttributes::bbcenter_to_rear) . The orientation of the vehicle’s coordinate system is equal to the orientation of the vehicle’s bounding boxMovingObject::base.BaseMoving::orientation.
-
optional MountingPosition osi3::SensorView::mounting_position_rmse = 5 The root mean squared error of the mounting position.
-
optional HostVehicleData osi3::SensorView::host_vehicle_data = 6 Host vehicle data.
Host vehicle data is data that the host vehicle knows about itself, e.g. from location sensors, internal sensors and ECU bus data, etc., that is made available to sensors as input.
-
optional GroundTruth osi3::SensorView::global_ground_truth = 7 Ground truth w.r.t. global coordinate system.
This is the ground truth that is provided to the sensor model by the simulation environment. It may be filtered as per the requirements of the sensor model as expressed by the
SensorViewConfigurationmessage(s) that where exchanged during the simulation initialization phase.- Note
The host vehicle is always contained in the ground truth provided, regardless of any filtering. The ground truth MUST contain at least as much of the ground truth data, as is requested by the sensor model, but MAY always contain more data, since the filtering is intended only as an optimization mechanism, not as a replacement of a proper sensor field of view modeling.
-
optional Identifier osi3::SensorView::host_vehicle_id = 8 The ID of the host vehicle in the
global_ground_truthdata.
-
repeated GenericSensorView osi3::SensorView::generic_sensor_view = 1000 Generic SensorView(s).
- Note
OSI uses singular instead of plural for repeated field names.
-
repeated RadarSensorView osi3::SensorView::radar_sensor_view = 1001 Radar-specific SensorView(s).
- Note
OSI uses singular instead of plural for repeated field names.
-
repeated LidarSensorView osi3::SensorView::lidar_sensor_view = 1002 Lidar-specific SensorView(s).
- Note
OSI uses singular instead of plural for repeated field names.
-
repeated CameraSensorView osi3::SensorView::camera_sensor_view = 1003 Camera-specific SensorView(s).
- Note
OSI uses singular instead of plural for repeated field names.
-
repeated UltrasonicSensorView osi3::SensorView::ultrasonic_sensor_view = 1004 Ultrasonic-specific SensorView(s).
- Note
OSI uses singular instead of plural for repeated field names.
-