Merge branch 'minor-docu-updates-wrt-gui' into 'develop'

Minor docu updates wrt GUI

See merge request !265

doc/source/index.rst

@@ -17,7 +17,7 @@ The openPASS (Open Platform for Assessment of Safety Systems) tool is a develope
 The simulation is based on a specific situation configuration and can contain several simulation runs, which differ due to random parameters.
 
 The software suite of openPASS started as a set of stand-alone applications, which can be installed and configured individually.
-Over time, especially the graphical user interface evolved to a single entry point, enabling the average user to use openPASS as a "monolithic" tool.
+In the future, the graphical user interface opGUI will evolve to a single entry point, enabling the average user to use openPASS as a "monolithic" tool.
 
 This guide contains information about installation, configuration and usage of all tools in the |Op| environment.
 
@@ -28,11 +28,6 @@ This guide contains information about installation, configuration and usage of a
 
    installation_guide/*
 
-.. TODO:: Update section for new react GUI.
-
-The GUI lets the user configure the simulation and generate configuration files from all set parameters.
-Based on these the simulation core calculates different simulation runs and compiles trace files for further processing.
-
 .. toctree::
    :caption: User Guides
    :glob:

doc/source/user_guide/10_overview.rst

@@ -25,8 +25,8 @@ Let’s have a look at what that means:
 
 1. PCM Simulations: “Crash re-simulations”
 
-  * PCM of GIDAS: PreCrash Matrix from the database of the German In-Depth Accident Study
-  * Re simulate real crashes from the past, but with cars having ADAS or AD functions and asses if the tested technology would have improved the safety.
+  * PCM of GIDAS: PreCrash Matrix with trajectories from the database of the German In-Depth Accident Study
+  * Re-simulate real crashes from the past, but with cars having ADAS or AD functions and assess if the tested technology would have improved the safety.
 
 2. (Traffic-)scenario based simulations
 

doc/source/user_guide/tutorials/10_scenario_simulation.rst

@@ -24,9 +24,7 @@ The ego vehicle is equipped with an AEB system (the system under test).
 The scenario agent performs a cut-in and triggers as a result the AEB system of the ego agent. 
 To force this exact maneuver, the scenario agent is set up to follow a predefined trajectory.
 
-.. TODO:: Update this paragraph for the new react GUI.
-
-The GUI is not yet capable of configuring and executing a scenario based simulation as this is currently work in progress. 
+The opGUI is not yet capable of configuring and executing a scenario based simulation as this is currently work in progress. 
 Thus, an existing simulation configuration is used and the simulation is started manually.
 
 **Step-by-step instructions**
@@ -69,7 +67,7 @@ Thus, an existing simulation configuration is used and the simulation is started
                 
         ii. Navigate to the directory ``examples/Configurations``. Here, all folders contain special pre-configured simulations (which either can be used as demo cases or as end-to-end test cases primarily used for development). 
 
-        iii. Copy all files from the directory specifying the specific scenario you want to simulate (in our case all files from directory ``examples/Configurations/AEB_CutIn``) to the directory ``configs``. Overwrite existing files when prompted. 
+        iii. Copy all files from the directory specifying the specific scenario you want to simulate (in our case all files from directory ``examples/Configurations/AEB_CutIn``) to the directory ``configs``. Overwrite existing files when prompted. The catalogs for vehicles or pedestrian parameters must be stored in a child folder ``Vehicles``.
 
     .. note::
 
@@ -82,13 +80,14 @@ Thus, an existing simulation configuration is used and the simulation is started
     ::
 
         configs
-        ├── PedestrianModelsCatalog.xosc
+        ├── Vehicles
+        │   ├── VehicleModelsCatalog.xosc
+        │   └── PedestrianModelsCatalog.xosc
         ├── ProfilesCatalog.xml
         ├── Scenario.xosc
         ├── SceneryConfiguration.xodr
         ├── simulationConfig.xml
-        ├── systemConfigBlueprint.xml
-        └── VehicleModelsCatalog.xosc
+        └── systemConfigBlueprint.xml
 
 
    As an example, modifications of the configuration files that describe an AEB cut-in scenario are given.

doc/source/user_guide/tutorials/20_pcm_simulation.rst

@@ -15,4 +15,4 @@ PCM Simulation
 ==============
 
 .. todo::
-   Write tutorial for PCM simulation
\ No newline at end of file
+   Include link and explaination to opGUI documentation how to run PCM simulations
\ No newline at end of file