You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/releases/v02.00.adoc
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,26 +6,27 @@ This is the initial version of the Open Simulation Interface (OSI).
6
6
== Overview
7
7
8
8
OSI is a generic interface for the environmental perception of automated driving functions in virtual scenarios.
9
-
It has been primarily conceived to enable easy and straightforward compatibility between automated driving functions and the variety of driving simulation frameworks that are available.
10
-
The data description has been derived from the perspective of sensor modeling for automated testing and validation of highly automated driving functions.
9
+
It is primarily conceived to enable easy and straightforward compatibility between automated driving functions and the variety of driving simulation frameworks available.
10
+
The data description has been derived from the perspective of sensor modeling for automated test and validation of highly automated driving functions.
11
11
12
12
== Implementation
13
13
14
-
OSI primarily contains an object based environment description using the message format of the protocol buffers library, which Google has developed and maintains.
14
+
OSI primarily contains an object based environment description using the message format of the protocol buffers librarydeveloped and maintained by Google.
15
15
16
16
== Detailed description
17
17
18
-
Top-level interfaces::
18
+
19
+
Top level interfaces::
19
20
OSI consists of two individual top level interfaces for object data: The ``OSI::GroundTruth`` and the ``OSI::SensorData`` interface.
20
21
+
21
-
* The ``OSI::GroundTruth`` interface provides an exact view of the simulated objects in a global coordinate system.
22
-
This message is populated using the internally available data of the used (driving)simulation framework and then published to external subscribers with an exporter plugin.
22
+
* The ``OSI::GroundTruth`` interface provides an exact view on the simulated objects in a global coordinate system.
23
+
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.
23
24
* The ``OSI::SensorData`` interface describes the objects in the reference frame of a sensor for environmental perception.
24
-
It is generated from an ``OSI::GroundTruth`` message and can either be used to directly connect to an automated driving function using ideal simulated data, or it may serve as an input for a sensor model simulating limited perception as a replication of real world sensor behavior.
25
+
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.
25
26
26
-
Low-level interfaces::
27
+
Lowlevel interfaces::
27
28
+
28
-
In addition to the two top-level interfaces, OSI contains an ``OSI::LowLevelData`` message.
29
+
Additionally to the two toplevel interfaces, OSI contains an ``OSI::LowLevelData`` message.
29
30
This message describes the output of a (physical) model of the measurement process before tracking and object hypothesis.
30
-
It does not deal with object data, but may comprise the geometrical influence of 3D simulations, for example, generating Lidar point clouds with a ray-tracer plugin.
31
-
This message also supports generic radar reflection lists and will be extended to supporting low-level camera data in the future.
31
+
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.
32
+
In addition this message supports generic radar reflection lists and will be extended to supporting lowlevel camera data in the future.
Copy file name to clipboardExpand all lines: doc/releases/v03.00.adoc
+21-21Lines changed: 21 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
== Purpose
4
4
5
-
This release is a complete rework and includes feedback from many OSI users.
5
+
This release is a complete rework including the feedback from many OSI users.
6
6
Thank you!
7
7
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.
8
8
@@ -12,46 +12,46 @@ We are aligned with the ongoing discussions for the upcoming ISO 23150 standard
12
12
* Added new top-level messages (new concept SensorView (Configuration),etc.).
13
13
** GroundTruth.
14
14
** SensorView.
15
-
** SensorData/FeatureData.
15
+
** SensorData / FeatureData.
16
16
** SensorViewConfiguration (used for auto-configuration of SensorView).
17
17
* Added technology-specific SensorView sub-messages to aid physical models.
18
18
* Introduced conceptual separation of “SensorModels” and “LogicModels”.
19
-
* Extended enumerations (for example, traffic sign type according to StVO and vehicle type).
19
+
* Extended enumerations (e.g. traffic sign Type according to StVO, vehicle Type, etc.).
20
20
* Improved messages and definitions (additional RoadConditions, country code in GT, AmbientIllumination, etc.).
21
-
* Introduced ISO 8855 coordinate systems (incompatible with earlier OSI versions).
21
+
* Use ISO 8855 coordinate systems (incompatible with earlier OSI versions).
22
22
* Redefined DetectedXXX messages.
23
23
* Introduced DetectedStationaryObjects.
24
24
* Merged MovingObjects and Vehicle messages.
25
25
* Redefined Lane messages (with separated lane boundary messages and intersections).
26
26
* Redefined TrafficLight messages.
27
-
* Redefined TrafficSigns (1 x MainSign + n x SupplementarySign including BaseStationary).
27
+
* Redefined TrafficSigns (1 x MainSign + n x SupplementarySign inclusive BaseStationary).
28
28
* New FeatureData messages (rework of previous LowLevelData message) - aligned with an upcoming standard ISO 23150.
29
-
* Made FeatureData usable for fusion units.
30
-
* Extended and clarified the existing doxygen documentation.
29
+
* FeatureData usable for fusion units.
30
+
* Extension and clarification of the existing doxygen documentation.
31
31
* Improved doxygen collaboration diagrams.
32
-
* Improved Build process and added install targets.
32
+
* Build process improvements, added install targets.
33
33
* Made proto definitions compatible with proto3 restrictions to allow concurrent use with proto3-only implementations in the future.
34
34
* Fixed version-checking of transmitted data.
35
-
* AND MUCH MORE, SO PLEASE ENJOY!!!
35
+
* AND MUCH MORE ENJOY!!!
36
36
37
-
https://github.com/OpenSimulationInterface/open-simulation-interface/files/2297162/osi_overview_v2.2_vs_v3.0.pdf>[For more information, view the `changelog`]
37
+
https://github.com/OpenSimulationInterface/open-simulation-interface/files/2297162/osi_overview_v2.2_vs_v3.0.pdf>[See for more information the `changelog`]
38
38
39
39
= https://github.com/OpenSimulationInterface/open-simulation-interface/releases/tag/v3.0.1[v3.0.1 - OSI "Cosmic Coulthard", Update 1]
40
40
41
-
https://www.youtube.com/watch?v=yG0oBPtyNb0[Summer time :)]
* **Bug Fix**: Changed open_simulation_interface target back from being a static library to its previous state as a shared library (this reverts an inadvertent change in v3.1.0 from previous releases).
31
-
v3.1.0 breaks all users of the shared library (that is, everyone building on Linux/Unix systems, and even some using the DLL on Windows).
30
+
* **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).
31
+
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).
32
32
33
33
= https://github.com/OpenSimulationInterface/open-simulation-interface/releases/tag/v3.1.2[v3.1.2 - OSI "Dynamic Duncan", Update 2]
It was previously the case that the company BMW AG organized most of the work on the OSI project.
8
-
To make it possible for as many interested parties as possible to contribute to the success of the Open Simulation Interface, the project has been transferred to https://www.asam.net/[ASAM e.V.].
9
-
This has been made public in the https://www.asam.net/news-media/news/detail/news/bmw-transfers-open-simulation-interface-osi-to-asam/[ASAM press release].
10
-
A new chapter in the development of OSI has been opened with the https://www.asam.net/conferences-events/detail/asam-osi-kick-off-workshop/[kickoff workshop], which will hopefully generate lots of project proposals to streamline the efficient future development of the interface.
11
-
Whith this release, we therefore decided to focus on improving processes and documentation.
7
+
The work on the OSI project was until now mainly organized by the BMW AG.
8
+
In order to enable as many interested parties as possible to contribute to the success of the Open Simulation Interface the project has been transferred to the https://www.asam.net/[ASAM e.V.] which has been made public in the https://www.asam.net/news-media/news/detail/news/bmw-transfers-open-simulation-interface-osi-to-asam/[ASAM press release].
9
+
A new chapter in the development of OSI is now opened with the https://www.asam.net/conferences-events/detail/asam-osi-kick-off-workshop/[kickoff workshop] leading to hopefully many project proposals streamlining the efficient future development of the interface.
10
+
Due to this we decided to focus on the improvement of processes and documentation with this release.
* Updated README according to K(eep) I(t) S(imply) S(tupid) principle.
17
-
* Added Issue and Pullrequest templates.
18
-
* Updated Travis CI.
19
-
** Updated to bionic 18.04.
20
-
** Added tests for building protobuf 2.6 and 3.0 in parallel.
21
-
** Bugfixed the display of doubled documentation.
22
-
* Fixed several typos in the comments.
23
-
* Added a centralized documentation in https://github.com/OpenSimulationInterface/osi-documentation[OSI-Documentation].
24
-
** Added contributors guidelines.
25
-
** Added commenting style guidelines.
26
-
** Added a uniform citation style based on APA.
27
-
** Updated installation guides for osi in Linux and Windows.
28
-
** Added a reference in sphinx based on generated doxygen documentation.
29
-
* Added rules to the comments to enforce osi message validation with the https://github.com/OpenSimulationInterface/osi-validation[OSI-Validator].
30
-
* Added the rule definitions in the rules.yml.
31
-
* Modularized testing of commenting style into python unit tests.
32
-
* Defined a standardized file format for reading trace files (*.osi).
33
-
* Defined naming conventions for osi files.
34
-
* Added a *.txt to *.osi file converter for backward compatibility.
35
-
* Added a script to make traces readable for plausibility checks.
36
-
* Corrected the citing style for OSI Bibtex.
37
-
* Corrected unit specifications and references according to DIN (for example, removed Unit: []).
38
-
* Added a timestamp in osi_environment.
39
-
* Added is_out_of_service bool to traffic light / traffic sign.
15
+
* Updated README according to K(eep) I(t) S(imply) S(tupid) principle
16
+
* Added Issue and Pullrequest templates
17
+
* Travis CI updated
18
+
** Update to bionic 18.04
19
+
** Added tests for building protobuf 2.6 and 3.0 in parallel
20
+
** Bugfixed the display of doubled documentation
21
+
* Fixed several typos in the comments
22
+
* Added a centralized documentation in https://github.com/OpenSimulationInterface/osi-documentation[OSI-Documentation]
23
+
** Added contributors guidelines
24
+
** Added commenting style guidelines
25
+
** Added uniform citation style according to APA
26
+
** Updated installation guides for osi in Linux and Windows
27
+
** Added a reference in sphinx based on the generated doxygen documentation
28
+
* Added rules to the comments in order to enforce osi message validation with the https://github.com/OpenSimulationInterface/osi-validation[OSI-Validator]
29
+
* Added the rule definitions in the rules.yml
30
+
* Modularized testing of commenting style into python unit tests
31
+
* Defined a standardazied a file format for reading trace files (*.osi)
32
+
* Defined naming conventions of osi files
33
+
* Added a *.txt to *.osi file converter for backward compatibility
34
+
* Added a script to make traces readable for plausibility checks
35
+
* Corrected the citing style for OSI Bibtex
36
+
* Corrected unit specifications and references according to DIN (e.g. removed Unit: [])
37
+
* Added timestamp in osi_environment
38
+
* Added is_out_of_service bool to traffic light / traffic sign
0 commit comments