Draft: Conan integration
Compare changes
Files
765+ 21
− 9
@@ -45,7 +45,7 @@ The following shows an (beautified) excerpt of the such an actual behavior tree,
@@ -58,7 +58,7 @@ For example, a `Condition` object holds either a `ByEntityCondition` or a `ByVal
@@ -164,12 +164,12 @@ So reaching the end of the function is literally an exception:
@@ -179,7 +179,7 @@ In other words `SimulationTimeCondition` will become the direct child `Condition
@@ -211,12 +211,12 @@ Yet, no `Action` node exist as intermediate layer.
@@ -301,7 +301,7 @@ Condition leaves have two responsibilities:
@@ -341,3 +341,15 @@ Action leaves have two responsibilities:
It consists of an ILogger interface class, which is passed to the OpenScenarioEngine on construction and therefore can be implemented outside of the OpenScenarioEngine. The OpenScenarioEngine forwards all log messages to the implementation of ILogger. The implementation of the ILogger interface class can then forward log messages of the OpenScenarioEngine to own logging implementations of a simulator or test framework.
- if scenarios contain semantically wrong information the OpenScenarioEngine can currently only detect this upon execution of the feature and therefore also stops the execution by **throwing a runtime error**. In the future semantic checks could also partially be implemented in the OpenScenario API (parser & validator), so semantic errors in scenarios could also be detected in the "validation only" use-case