Skip to content

Conversation

@pmai
Copy link
Contributor

@pmai pmai commented Jun 23, 2021

This PR is a consolidated rebased preview of all of the documentation migration changes which are also available as separate PRs against the migration branch.

This was created to allow easier at a glance review of the documentation changes in one place. Will be kept up-to-date until merge.

max-rosin added 19 commits June 23, 2021 12:26
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
…ocs (#534)

Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
Signed-off-by: Maximilian Rosin <maximilian.rosin@parson-europe.com>
@pmai pmai added the Documentation Everything which impacts the quality of the documentation and guidelines. label Jun 23, 2021
@pmai pmai added this to the V3.4.0 milestone Jun 23, 2021
@pmai pmai self-assigned this Jun 23, 2021
@@ -0,0 +1,3 @@
= Releases

ss No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed in context of PR #533 (4d42c5b).


https://www.youtube.com/watch?v=SJUhlRoBL8M[Think p(OSI)tive!]


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed whitespace in context of PR #533 (9ac1d74).

= https://github.com/OpenSimulationInterface/open-simulation-interface/releases/tag/v3.3.1[v3.3.1 - OSI "Fabulous Fangio", Update 1]

== https://github.com/OpenSimulationInterface/open-simulation-interface/milestone/18?closed=1[Content/Changes]

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed whitespace in context of PR #533 (9ac1d74).


== 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!
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed linebreaks in context of PR #533 (9ac1d74).

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.

https://github.com/OpenSimulationInterface/open-simulation-interface/pulls?page=1&q=is%3Apr+is%3Aclosed+milestone%3Av3.0.0[Content/Changes]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added missing header markup in context of PR #533 (9ac1d74).


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

https://github.com/OpenSimulationInterface/open-simulation-interface/pulls?page=1&q=is%3Apr+is%3Aclosed+milestone%3Av3.0.1[Content/Changes]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added missing header markup in context of PR #533 (9ac1d74).

@@ -0,0 +1,21 @@
= OSI trace file naming conventions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add example in context of PR #528 (5ba5394).

@@ -0,0 +1,18 @@
= OSI trace file formats

There are multiple formats for storing multiple serialized OSI messages into one trace file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed typo in context of PR #528 (5ba5394).

@@ -0,0 +1,48 @@
# Trace-file formatting scripts
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed typos in context of PR #528 (5ba5394).

@@ -0,0 +1,26 @@
= Reference points and coordinate systems
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See PR #516

@@ -0,0 +1,11 @@
= The vision of Open Simulation Interface
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See issue #540

@max-rosin
Copy link
Contributor

Fixed all the issues I found in the corresponding PRs (see comments).


OSI contains an object-based environment description using the message format of the https://github.com/protocolbuffers/protobuf/wiki[Protocol Buffer] library developed and maintained by Google.
OSI defines top-level messages that are used to exchange data between separate models.
Top-level messages define the ``GroundTruth`` interface, the ``SensorData`` interface and, since OSI version 3.0.0, the ``SensorView``, ``SensorViewConfiguration`` and ``FeatureData`` interfaces.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TrafficCommand and TrafficUpdate missing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove comment, gets clear below.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also fell over that here: https://github.com/OpenSimulationInterface/open-simulation-interface/pull/535/files
let's add an
Top-level messages regarding sensor models define...

Environmental effect models consume sensor-view data and produce sensor-view data.
Environmental effect models may, for example, include the following:

* Shadows and oclusion
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Shadows and oclusion
* Shadows and occlusion

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe Shadows and occlusions (since we used plural for shadows than to stay consistent, also use it for occlusions)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed typo and switched to plural, see 8a14884.

@clemenshabedank
Copy link
Contributor

Won't be able to work on reviewing in the next 3 weeks due to vacation. I apologize.

However, this does not mean that filling the field is optional.
For the purpose of providing a complete interface, all existing fields should be set, unless not setting a field carries a specific meaning as indicated in the accompanying comment.

All field numbers of 10000 and upward are available for user-specific extensions via custom fields.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
All field numbers of 10000 and upward are available for user-specific extensions via custom fields.
All field numbers of 10000 and above are available for user-specific extensions via custom fields.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See 9e24025

Environmental effect models consume sensor-view data and produce sensor-view data.
Environmental effect models may, for example, include the following:

* Shadows and oclusion
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe Shadows and occlusions (since we used plural for shadows than to stay consistent, also use it for occlusions)


* Shadows and oclusion
* Weather effects
* Physics of a sensor
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is meant by "Physics of a sensor" ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The actual physics of a sensor, for example, its optics, electronics, and mechanics. We had discussion about this last year (in October if I remember correctly). So I thought, I may just include it here.

Comment on lines +1 to +5
= Feature data

Feature data contains detected features in the reference frame of a sensor.
Feature data is generated from ground-truth data.
It serves, for example, as input for sensor models simulating object detection or feature fusion models.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feature data needs more description, I feel that it is still vague.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that the topic can be expanded. Do you have any suggestions? What are you missing?

@@ -0,0 +1,48 @@
# Trace-file formatting scripts

OSI provides Python scripts for converting trace files from one format to the other.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
OSI provides Python scripts for converting trace files from one format to the other.
Python scripts are provided for converting trace files from one format to the other.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Improved wording ("OSI repo contains...") while maintaining active mode (see 3806ef0).

Logical models consume sensor-data data and produce sensor-data data.

An example of a logical model is a sensor-fusion model, which fuses the output of multiple sensor models.
Another use case is the injection of faults after the sensor model.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"injection of faults" does not seem a good choice of words. Let's see how to replace it!

@@ -0,0 +1,26 @@
= Reference points and coordinate systems

With Open Simulation Interface, an object's position coordinates refer to the center of the object's bounding box.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
With Open Simulation Interface, an object's position coordinates refer to the center of the object's bounding box.
In Open Simulation Interface, object's position is defined by the coordinates of it's center of bounding box.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #516 for current changes.

= Reference points and coordinate systems

With Open Simulation Interface, an object's position coordinates refer to the center of the object's bounding box.
This reference point is not necessarily identical to the origin of the respective coordinate systems.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"respective coordinate system" is a bit confusing

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed. See #516 for current changes.

@stefancyliax stefancyliax removed this from the V3.4.0 milestone Aug 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Everything which impacts the quality of the documentation and guidelines.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants