OSI “Dynamic Duncan”, Update 2

Content/Changes:

• Bugfix:
  The version number is now correct in the VERSION file.

OSI “Dynamic Duncan”, Update 1

Content/Changes:

• Bug Fix:
  Changed open_simulation_interface target back from being a static library to a shared library, as before (this reverts an inadvertent change in v3.1.0 from previous releases).
  v3.1.0 breaks all users of the shared library (i.e. everyone building on Linux/Unix systems, and even some using the DLL on Windows).

OSI “Dynamic Duncan”

(O SI)lent night

Purpose:

This time of the year Santa comes with presents and has also thought about the sensor modelers of this planet. We introduce the current state of the ISO 23150 discussions including Ultrasonic and Camera Detections. The traffic signs have been reworked and the documentation has been extended for a perfect user experience. Trust me - it's amazing!

Content/Changes:

• Complete rework of traffic signs including images in documentation.
• Added Camera Detections in osi_featuredata.proto.
• Added Ultrasonic Detections in osi_featuredata.proto.
• Introduced light states for emergency and service vehicles.
• Added orientation_acceleration and updated formulas.
• Extended documentation with svg images.
• Added model_reference for static and moving objects.
• Added map_reference in ground truth.
• Added proj4 string for coordinate transformations.
• Introduced raster_lidar_proposal from innoviz.
• Improved documentation with HTML tables and images for all traffic signs.

OSI "Cosmic Coulthard", Update 1

SUMMER TIME

Purpose:

This release is a patch reworking parts of the documentation in order to avoid ambiguities and improving the build/installation process of OSI.

Content/Changes:

• Added script to automatically convert the messages from proto2 to proto3 with on the wire compatibility
• cmake enhancements to enable multi-version support of OSI 2 and OSI 3
• Added Python 3 support
• Clarification of multiple comments
• Added explanatory images in the documentation
• centerline definition improved
• signal_strength definition in LidarSensorView corrected
• FeatureData::ambiguity_id definition clarified
• RadarSensorViewConfiguration::AntennaDiagram::response definition clarified

OSI "Cosmic Coulthard"

OSI ET ORBI

Purpose:

This release is a complete rework including the feedback from many OSI users. Thank you!
We are aligned with the ongoing discussions for the upcoming ISO 23150 standard for hardware sensor outputs in order to bring simulation and the hardware in the car closer together.

Content/Changes:

• Added major version to package label (osi3), allowing concurrent use of OSI 2.x and OSI 3.x in one process.
• Added new top-level messages (new concept SensorView (Configuration), etc.).
  1. GroundTruth.
  2. SensorView.
  3. SensorData / FeatureData.
  4. SensorViewConfiguration (used for auto-configuration of SensorView).
• Added technology-specific SensorView sub-messages to aid physical models.
• Introduced conceptual separation of “SensorModels” and “LogicModels”.
• Extended enumerations (e.g. traffic sign Type according to StVO, vehicle Type, etc.).
• Improved messages and definitions (additional RoadConditions, country code in GT, AmbientIllumination, etc.).
• Use ISO 8855 coordinate systems (incompatible with earlier OSI versions).
• Redefined DetectedXXX messages.
• Introduced DetectedStationaryObjects.
• Merged MovingObjects and Vehicle messages.
• Redefined Lane messages (with separated lane boundary messages and intersections).
• Redefined TrafficLight messages.
• Redefined TrafficSigns (1 x MainSign + n x SupplementarySign inclusive BaseStationary).
• New FeatureData messages (rework of previous LowLevelData message) - aligned with an upcoming standard ISO 23150.
• FeatureData usable for fusion units.
• Extension and clarification of the existing doxygen documentation.
• Improved doxygen collaboration diagrams.
• Build process improvements, added install targets.
• Made proto definitions compatible with proto3 restrictions to allow concurrent use with proto3-only implementations in the future.
• Fixed version-checking of transmitted data.
• AND MUCH MORE ENJOY!!!

OSI "Brave Brabham", Update 1

Purpose:

This release focuses on optimizing the build process and ensures the proper installation of different versions of OSI on a single system.

Content/Changes:

• Allowing several OSI versions on the same computer.
• Improves CI builds to also test the installation cmake targets for proper completion.

OSI "Brave Brabham"

Purpose:

This release focuses on optimizing the build process and documentation.

Content/Changes:

• Added a shared library target to the CMake build script.
• Generated a proper doxygen documentation.
• Placed the version number in one file (VERSION).
• Added unit testing mechanism including style guide checking.
• Redefined precipitation and added a fog definition to the environmental conditions message.
• Added layer id to low level point cloud data.
• Reworked large parts of the build instructions in the WIKI.

OSI "Agile Andretti"

Purpose:

This is the initial BASE VERSION for Tool Development.

Content/Changes:

• Added a CMake build script allowing users to integrate OSI into larger project build scripts.
• Added a python build script.
• Integrated automatic building and testing using the Travis CI service.
• Added a polygon base as an extension of the concept of a bounding box in order to be able to return an occluded shape different from a rectangle.
• Added a definition of pressure, temperature and precipitation in the environmental conditions message.

Remarks:

We will now release the versions using the name of a Formula 1 driver!
Naming convention: "adjective + last name driver" -> Alliteration necessary!

OSI Initial Commit

This is the initial version of the Open Simulation Interface (OSI).

Overview:

OSI is a generic interface for the environmental perception of automated driving functions in virtual scenarios. It is primarily conceived to enable easy and straightforward compatibility between automated driving functions and the variety of driving simulation frameworks available. The data description has been derived from the perspective of sensor modelling for automated test and validation of highly automated driving functions.

Implementation:

OSI primarily contains an object based environment description using the message format of the protocol buffers library developed and maintained by Google.

Detailed description:

Top level interfaces:

OSI consists of two individual top level interfaces for object data: The OSI::GroundTruth and the OSI::SensorData interface.

• The OSI::GroundTruth interface provides an exact view on the simulated objects in a global coordinate system. This message is populated using the internally available data of the used (driving)-simulation framework and is afterwards published to external subscribers with an exporter plugin.
• The OSI::SensorData interface describes the objects in the reference frame of a sensor for environmental perception. It is generated from a OSI::GroundTruth message and can either be used to directly connect to an automated driving function using ideal simulated data, or may serve as input for a sensor model simulating limited perception as a replication of real world sensor behavior.

Low level interfaces:

Additionally to the two top level interfaces, OSI contains an OSI::LowLevelData message. This message describes the output of a (physical) model of the measurement process before tracking and object hypothesis. It does not deal with object data, but may comprise the geometrical influence of 3D simulations e.g. generating Lidar point clouds with a ray-tracer plugin. In addition this message supports generic radar reflection lists and will be extended to supporting low level camera data in the future.