Commit 0d056bbb authored by Pierre Mai's avatar Pierre Mai
Browse files

Add library concepts section, adjust WPs, add PMSF commitment

parent e7c5d076
Pipeline #1177 passed with stage
in 15 seconds
...@@ -119,6 +119,18 @@ Also included is the definition of the exact semantics of temporal composition o ...@@ -119,6 +119,18 @@ Also included is the definition of the exact semantics of temporal composition o
===== Considerations for 1.x ===== Considerations for 1.x
===== Library Concepts and Packaging (scenario definition & scenario execution) ===== Library Concepts and Packaging (scenario definition & scenario execution)
With the expected usage of scenarios at different abstraction levels, and it being aimed at different ODDs and different automated driving systems, the need for encapsulating scenarios in libraries is obvious.
The requirements for library concepts and packaging however stretch further than this:
Not only does the encapsulation of scenarios transitively require the packaging of dependencies of the scenario, like modifiers, extended atomic scenarios, domain extensions, and referenced resources, like e.g. models;
rather these entities themselves could/should form the basis of reusable libraries or modules by themselves, since they can form the basis for more powerful scenario creation methods.
Additionally it should be easy to specify and extract meta data, tags and classifications from libraries that will be used to characterize libraries and thereby help in locating suitable libraries for a given use case (consider e.g. smart scenario databases driven by the semantics of the language rather than the usual add-on tagging of meta data).
Since packaging will have to deal with resources referenced in libraries like e.g. models, which might not be as portable as the OpenSCENARIO 2.0 itself, the packaging mechanisms have to include the ability to specify such dependencies while allowing for divergence in implementation to cater to different implementations.
Another dimension of the library concepts and packaging work will addressing its relationship with OpenSCENARIO 1.x catalog concepts, and future evolution thereof.
===== Measurement and Success Criteria ===== Measurement and Success Criteria
This section will outline the OpenScenario 2.0 features used to collect and classify information during scenario execution. The collected information will be used to evaluate the quality and extent of the verification process, as well as the performance of the "ego" actor. This section will outline the OpenScenario 2.0 features used to collect and classify information during scenario execution. The collected information will be used to evaluate the quality and extent of the verification process, as well as the performance of the "ego" actor.
......
...@@ -55,9 +55,11 @@ A breakdown of the project into individual work packages and the corresponding e ...@@ -55,9 +55,11 @@ A breakdown of the project into individual work packages and the corresponding e
| *WP Number* | LC-Expressions | *WP Number* | LC-Expressions
| *Responsibles* | P. Mai, J. Krasser | *Responsibles* | P. Mai, J. Krasser
|*Title / Description* | Expression language for OpenSCENARIO 2.0 |*Title / Description* | Expression language for OpenSCENARIO 2.0
|*Deliverable* | Full semantic description of the expression language of the OpenSCENARIO 2.0 language. Input for LC-Syntax on syntax aspects of the expression language.
| *Effort (Man-days)* |Estimated work effort to complete this WP. This comprises the generic parts of expressions (e.g. arithmetic, logic, etc.) based on the properties of the domain model, as well as ways to define more complex domain-specific expressions.
| *Service Provider* | Tasks to be performed by a service provider. Also estimate the % of total effort for this WP. |*Deliverable* | Full semantic description of the expression language of the OpenSCENARIO 2.0 language. Input for LC-Syntax on syntax aspects of the expression language.
| *Effort (Man-days)* | 50 person days
| *Service Provider* | Documentation of expression language parts of the specification. ~25% of effort.
|=== |===
.WP LC-Semantics .WP LC-Semantics
...@@ -65,7 +67,8 @@ A breakdown of the project into individual work packages and the corresponding e ...@@ -65,7 +67,8 @@ A breakdown of the project into individual work packages and the corresponding e
|=== |===
| *WP Number* | LC-Semantics | *WP Number* | LC-Semantics
| *Responsibles* | I. Whiteside, Y. Hollander (maybe), S. Rosenberg (maybe) | *Responsibles* | I. Whiteside, Y. Hollander (maybe), S. Rosenberg (maybe)
|*Title / Description* | A well-defined semantics for OpenSCENARIO 2.0. |*Title / Description* | A well-defined semantics for OpenSCENARIO 2.0.
As the levels of abstraction have been raised, so the effort and understanding needed for a simulation engine to implement support for this standard is raised. As such, the semantics of a scenario become more important: to give an unambiguous understand of a) whether that scenario could be executed at all; b) whether that scenario could be executed on a given map; c) how to execute that scenario unambigously. As the levels of abstraction have been raised, so the effort and understanding needed for a simulation engine to implement support for this standard is raised. As such, the semantics of a scenario become more important: to give an unambiguous understand of a) whether that scenario could be executed at all; b) whether that scenario could be executed on a given map; c) how to execute that scenario unambigously.
|*Deliverable* | Semantic rules for the OpenSCENARIO 2.0 language. |*Deliverable* | Semantic rules for the OpenSCENARIO 2.0 language.
| *Effort (Man-days)* | Estimated work effort: 100 man-days | *Effort (Man-days)* | Estimated work effort: 100 man-days
...@@ -77,9 +80,11 @@ As the levels of abstraction have been raised, so the effort and understanding n ...@@ -77,9 +80,11 @@ As the levels of abstraction have been raised, so the effort and understanding n
| *WP Number* | LC-Libraries | *WP Number* | LC-Libraries
| *Responsibles* | P. Mai, Y. Hollander | *Responsibles* | P. Mai, Y. Hollander
|*Title / Description* | Libraries, Modules, Packaging and Namespace aspects of OpenSCENARIO 2.0 |*Title / Description* | Libraries, Modules, Packaging and Namespace aspects of OpenSCENARIO 2.0
This WP will address the necessary ways of packaging functionality into libraries and modules in ways that foster re-use across users and implementations. Related namespacing problems are addressed. Relation to OpenSCENARIO 1.0 re-use concepts will be addressed.
|*Deliverable* |Full semantic description of the library, modules, packaging and namespace aspects of the OpenSCENARIO 2.0 language. Input for LC-Syntax on syntax aspects of the libraries, modules, packaging and namespaces aspects. |*Deliverable* |Full semantic description of the library, modules, packaging and namespace aspects of the OpenSCENARIO 2.0 language. Input for LC-Syntax on syntax aspects of the libraries, modules, packaging and namespaces aspects.
| *Effort (Man-days)* |Estimated work effort to complete this WP. | *Effort (Man-days)* | 50 person days
| *Service Provider* | Tasks to be performed by a service provider. Also estimate the % of total effort for this WP. | *Service Provider* | Documentation of library, modules, packaging and namespace parts of the specification. ~15% of effort.
|=== |===
.WP LC-Transfer1x .WP LC-Transfer1x
......
...@@ -8,7 +8,7 @@ Member companies contribute resources for the project as per the following table ...@@ -8,7 +8,7 @@ Member companies contribute resources for the project as per the following table
| Company (Name, Location) | Committed Work (man-days) | Participant contact details (name, phone, email) | Company (Name, Location) | Committed Work (man-days) | Participant contact details (name, phone, email)
|DLR | | |DLR | |
|Foretellix | | |Foretellix | |
|PMSF | | |PMSF |30 | Pierre R. Mai, +49-8161-97696-11, pmai@pmsf.eu
|BTC | | |BTC | |
|APTIV | | |APTIV | |
|AVL | | |AVL | |
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment