Updated feedback button behavior

philipwindecker · philipwindecker · commit 86b2b1eee4a3 · 2022-09-15T13:46:27.000+02:00
Signed-off-by: Philip Windecker &lt;philip.windecker@avenyr.de&gt;
diff --git a/doc/_config.adoc b/doc/_config.adoc
@@ -8,6 +8,7 @@ ifndef::root-path[:root-path: ./]
 :partials-path: {root-path}../_additional_content
 :asciidoc-resources: ../asciidoc-resources
 :appendix-caption: Annex
+:page-feedbackurl: https://github.com/OpenSimulationInterface/open-simulation-interface/issues/new
 
 // ifndef::use-antora-rules,include-only-once[]
 ifndef::include-only-once[]
diff --git a/doc/architecture/architecture_overview.adoc b/doc/architecture/architecture_overview.adoc
@@ -1,9 +1,8 @@
-= Overview of OSI architecture
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Overview of OSI architecture
 
 OSI contains an object-based environment description that uses the message format of the https://github.com/protocolbuffers/protobuf/wiki[Protocol Buffer] library.
 Google developed and maintains the Protocol Buffer library.
diff --git a/doc/architecture/data_layer.adoc b/doc/architecture/data_layer.adoc
@@ -1,9 +1,8 @@
-= Data layer
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Data layer
 
 The OSI data layer is defined in the message specifications using the ProtoBuf IDL cite:[protobuf].
 This defines the data that can be transmitted using OSI, including the structure and the semantics of the data.
diff --git a/doc/architecture/environmental_effect_model.adoc b/doc/architecture/environmental_effect_model.adoc
@@ -1,9 +1,8 @@
-= Environmental effect model
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Environmental effect model
 
 Environmental effect models consume `SensorView` messages and produce `SensorView` messages.
 Environmental effect models may, for example, alter `SensorView` messages to include effects and phenomena caused by:
diff --git a/doc/architecture/feature_data.adoc b/doc/architecture/feature_data.adoc
@@ -1,9 +1,8 @@
-= Feature data
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Feature data
 
 `FeatureData` messages contain detected features in the reference frame of a sensor.
 `FeatureData` messages are generated from `GroundTruth` messages.
diff --git a/doc/architecture/formatting_scripts.adoc b/doc/architecture/formatting_scripts.adoc
@@ -1,9 +1,8 @@
-= Trace-file formatting scripts
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Trace-file formatting scripts
 
 The OSI repository contains Python scripts for converting trace files from one format to another.
 The formatting scripts are stored in `open-simulation-interface/format/`
diff --git a/doc/architecture/ground_truth.adoc b/doc/architecture/ground_truth.adoc
@@ -1,9 +1,8 @@
-= Ground truth
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Ground truth
 
 `GroundTruth` messages describe the simulated environment containing all simulated objects in the global coordinate system at consecutive time instances.
 They are based on data available to the simulation environment.
diff --git a/doc/architecture/logical_model.adoc b/doc/architecture/logical_model.adoc
@@ -1,9 +1,8 @@
-= Logical model
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Logical model
 
 Logical models consume `SensorData` messages and produce `SensorData` messages.
 
diff --git a/doc/architecture/packaging_layer.adoc b/doc/architecture/packaging_layer.adoc
@@ -1,9 +1,8 @@
-= Packaging layer
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Packaging layer
 
 The OSI packaging layer specifies how components that use the OSI data layer, for example, sensor models, are packaged for exchange.
 
diff --git a/doc/architecture/proto-files.adoc b/doc/architecture/proto-files.adoc
@@ -1,9 +1,8 @@
-= Protobuffer files
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Protobuffer files
 
 TODO: Add general description.
 
diff --git a/doc/architecture/reference_points_coordinate_systems.adoc b/doc/architecture/reference_points_coordinate_systems.adoc
@@ -1,9 +1,8 @@
-= Coordinate systems, reference points and coordinate transformation
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Coordinate systems, reference points and coordinate transformation
 
 OSI uses DIN ISO 8855:2013-11 cite:[iso8855] for coordinate systems and transformations between coordinate systems.
 OSI uses three coordinate systems:
diff --git a/doc/architecture/sensor_data.adoc b/doc/architecture/sensor_data.adoc
@@ -1,9 +1,8 @@
-= Sensor data
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Sensor data
 
 `SensorData` messages imitate the output of real sensors.
 They can be generated from `GroundTruth` messages, `SensorView` messages, `FeatureData` messages, or `SensorData` messages.
diff --git a/doc/architecture/sensor_model.adoc b/doc/architecture/sensor_model.adoc
@@ -1,9 +1,8 @@
-= Sensor model
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Sensor model
 
 Sensor models consume `SensorView` messages and produce `SensorData` messages.
 Sensor-model output does not represent raw data but detected features or classified objects.
diff --git a/doc/architecture/sensor_view.adoc b/doc/architecture/sensor_view.adoc
@@ -1,9 +1,8 @@
-= Sensor view
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Sensor view
 
 The sensor view provides the input to OSI sensor models.
 `SensorView` messages are derived from `GroundTruth` messages.
diff --git a/doc/architecture/sensor_view_configuration.adoc b/doc/architecture/sensor_view_configuration.adoc
@@ -1,9 +1,8 @@
-= Sensor-view configuration
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Sensor-view configuration
 
 The sensor view is flexibly defined to provide different kinds of sensor models with an appropriate input.
 The sensor-view configuration defines the configuration of a particular sensor view.
diff --git a/doc/architecture/test_scripts.adoc b/doc/architecture/test_scripts.adoc
@@ -1,9 +1,8 @@
-= Test scripts
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Test scripts
 
 TODO: Add general description.
 
diff --git a/doc/architecture/trace_file_formats.adoc b/doc/architecture/trace_file_formats.adoc
@@ -1,10 +1,9 @@
-[#top-osi_trace_file_formats]
-= OSI trace file formats
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+[#top-osi_trace_file_formats]
+= OSI trace file formats
 
 There are multiple formats for storing multiple serialized OSI messages in one trace file.
 
diff --git a/doc/architecture/trace_file_naming.adoc b/doc/architecture/trace_file_naming.adoc
@@ -1,9 +1,8 @@
-= OSI trace file naming conventions
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= OSI trace file naming conventions
 
 **Name format**
 
diff --git a/doc/architecture/traffic_command.adoc b/doc/architecture/traffic_command.adoc
@@ -1,9 +1,7 @@
-= Traffic command
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
-
+= Traffic command
 
 `TrafficCommand` messages contain control commands from the scenario engine to traffic participant models.
diff --git a/doc/architecture/traffic_participant.adoc b/doc/architecture/traffic_participant.adoc
@@ -1,9 +1,8 @@
-= Traffic participant
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Traffic participant
 
 A traffic participant is an element of the simulated world and can change its state during simulation time, for example, its position and orientation.
 A traffic participant represents one of the following:
diff --git a/doc/architecture/traffic_update.adoc b/doc/architecture/traffic_update.adoc
@@ -1,9 +1,8 @@
-= Traffic update
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Traffic update
 
 `TrafficUpdate` messages are provided by traffic participants.
 They provide updates on the position, state, and future trajectory of a traffic participant back to the simulation environment.
diff --git a/doc/architecture/vehicle_dynamics.adoc b/doc/architecture/vehicle_dynamics.adoc
@@ -1,8 +1,7 @@
-= Vehicle dynamics
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Vehicle dynamics
 
 TODO: Content to be added in future release.
diff --git a/doc/misc/osi_vision.adoc b/doc/misc/osi_vision.adoc
@@ -1,9 +1,8 @@
-= Idea behind Open Simulation Interface
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Idea behind Open Simulation Interface
 
 {THIS_STANDARD} Open Simulation Interface is a specification for interfaces between models and components of a distributed simulation.
 OSI is strongly focused on the environmental perception of automated driving functions.
diff --git a/doc/setup/including_osi_dev_projects.adoc b/doc/setup/including_osi_dev_projects.adoc
@@ -1,9 +1,8 @@
-= Including OSI in development projects
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Including OSI in development projects
 
 TODO: Content to be added in future release.
 
diff --git a/doc/setup/installing_linux_cpp.adoc b/doc/setup/installing_linux_cpp.adoc
@@ -1,9 +1,8 @@
-= Installing OSI for C++ on Linux
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Installing OSI for C++ on Linux
 
 **Prerequisites**
 
diff --git a/doc/setup/installing_linux_python.adoc b/doc/setup/installing_linux_python.adoc
@@ -1,9 +1,8 @@
-= Installing OSI for Python on Linux
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Installing OSI for Python on Linux
 
 **Prerequisites**
 
diff --git a/doc/setup/installing_macos.adoc b/doc/setup/installing_macos.adoc
@@ -1,9 +1,8 @@
-= Installing OSI on MacOS
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Installing OSI on MacOS
 
 TODO: Content to be added in future release.
 
diff --git a/doc/setup/installing_windows_cpp.adoc b/doc/setup/installing_windows_cpp.adoc
@@ -1,9 +1,8 @@
-= Installing OSI for C++ on Windows
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Installing OSI for C++ on Windows
 
 **Prerequisites**
 
diff --git a/doc/setup/installing_windows_python.adoc b/doc/setup/installing_windows_python.adoc
@@ -1,9 +1,8 @@
-= Installing OSI for Python on Windows
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Installing OSI for Python on Windows
 
 **Prerequisites**
 
diff --git a/doc/setup/using_osi_support_tools.adoc b/doc/setup/using_osi_support_tools.adoc
@@ -1,9 +1,8 @@
-= Using OSI supporting tools
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Using OSI supporting tools
 
 TODO: Content to be added in future release.
 
diff --git a/doc/usecases/benchmark_integration_gpu_radar.adoc b/doc/usecases/benchmark_integration_gpu_radar.adoc
@@ -1,9 +1,8 @@
-= Benchmarking and integration: OSI-GPU-radar
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Benchmarking and integration: OSI-GPU-radar
 
 TODO: Content to be added in future release.
 TODO: Clarify content of this use case and make title more clear
diff --git a/doc/usecases/fusing_sensor_outputs.adoc b/doc/usecases/fusing_sensor_outputs.adoc
@@ -1,9 +1,8 @@
-= Fusing sensor outputs
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Fusing sensor outputs
 
 TODO: Content to be added in future release.
 
diff --git a/doc/usecases/generating_osi_traces.adoc b/doc/usecases/generating_osi_traces.adoc
@@ -1,9 +1,8 @@
-= Generating OSI traces
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Generating OSI traces
 
 TODO: Content to be added in future release.
 
diff --git a/doc/usecases/injecting_faults.adoc b/doc/usecases/injecting_faults.adoc
@@ -1,9 +1,8 @@
-= Injecting faults
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Injecting faults
 
 TODO: Content to be added in future release.
 
diff --git a/doc/usecases/modeling_camera_electronics.adoc b/doc/usecases/modeling_camera_electronics.adoc
@@ -1,9 +1,8 @@
-= Modeling camera electronics
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Modeling camera electronics
 
 TODO: Content to be added in future release.
 
diff --git a/doc/usecases/modeling_lidar_sensor.adoc b/doc/usecases/modeling_lidar_sensor.adoc
@@ -1,9 +1,8 @@
-= Modeling a LIDAR sensor
-
 ifndef::include-only-once[]
 :root-path: ../
 include::{root-path}_config.adoc[]
 endif::[]
+= Modeling a LIDAR sensor
 
 // TODO: Add extensive description of this use case.
 
diff --git a/doc/usecases/modeling_traffic_participant.adoc b/doc/usecases/modeling_traffic_participant.adoc
diff --git a/doc/usecases/transforming_coordinate_systems.adoc b/doc/usecases/transforming_coordinate_systems.adoc
