diff --git a/.antora/modules/specification/images b/.antora/modules/specification/images new file mode 120000 index 00000000..7621b12b --- /dev/null +++ b/.antora/modules/specification/images @@ -0,0 +1 @@ +../../../content/_images \ No newline at end of file diff --git a/.antora/modules/specification/images/overview_open_x.png b/.antora/modules/specification/images/overview_open_x.png deleted file mode 100644 index 990ec256..00000000 Binary files a/.antora/modules/specification/images/overview_open_x.png and /dev/null differ diff --git a/.antora/modules/specification/pages b/.antora/modules/specification/pages new file mode 120000 index 00000000..f0bfb077 --- /dev/null +++ b/.antora/modules/specification/pages @@ -0,0 +1 @@ +../../../content \ No newline at end of file diff --git a/.antora/modules/specification/pages/_config.adoc b/.antora/modules/specification/pages/_config.adoc deleted file mode 100644 index 170830b5..00000000 --- a/.antora/modules/specification/pages/_config.adoc +++ /dev/null @@ -1,37 +0,0 @@ - -// This file contains AsciiDoc attributes that shall be used in every AsciiDoc file. -// NOTE: Its content is only applied for Asciidoctor! -// If the same attribute is defined in the antora.yml (without @), the antora.yml definition takes precedence for Antora. - -ifndef::root-path[:root-path: ./] - -:partials-path: {root-path}../_additional_content -:asciidoc-resources: ../asciidoc-resources -:appendix-caption: Annex - -// ifndef::use-antora-rules,include-only-once[] -ifndef::include-only-once[] -:GLO_VAR_STA_ASAM_OpenCRG: ASAM OpenCRG -:GLO_VAR_STA_ASAM_OpenDRIVE: ASAM OpenDRIVE -:GLO_VAR_STA_ASAM_OpenLABEL: ASAM OpenLABEL -:GLO_VAR_STA_ASAM_OpenODD: ASAM OpenODD -:GLO_VAR_STA_ASAM_OSI: ASAM OSI -:GLO_VAR_STA_ASAM_OpenSCENARIO: ASAM OpenSCENARIO -:GLO_VAR_STA_ASAM_OpenXOntology: ASAM OpenXOntology -:GLO_VAR_STA_BSI_PAS_1883: BSI PAS 1883 -:revnumber: --localbuild-- -:revdate: {docdate} -:bibtex-file: content/bibliography.bib -// Replace PLACEHOLDER with the name of your standard, e.g. OpenDRIVE -:THIS_STANDARD: ASAM OpenMATERIAL -:imagesdir: {root-path}/_images -:include-only-once: true -endif::[] - -ifndef::use-antora-rules[] -include::{asciidoc-resources}/preamble.adoc[] -endif::[] - -ifdef::env-gitlab[] -:relfilesuffix: .adoc -endif::[] diff --git a/.antora/modules/specification/pages/_images/overview_open_x.png b/.antora/modules/specification/pages/_images/overview_open_x.png deleted file mode 100644 index 990ec256..00000000 Binary files a/.antora/modules/specification/pages/_images/overview_open_x.png and /dev/null differ diff --git a/.antora/modules/specification/pages/bibliography.adoc b/.antora/modules/specification/pages/bibliography.adoc deleted file mode 100644 index acf5bf2a..00000000 --- a/.antora/modules/specification/pages/bibliography.adoc +++ /dev/null @@ -1,3 +0,0 @@ -= Bibliography -[bibliography] -bibliography::[] \ No newline at end of file diff --git a/.antora/modules/specification/pages/bibliography.bib b/.antora/modules/specification/pages/bibliography.bib deleted file mode 100644 index 0ac159ce..00000000 --- a/.antora/modules/specification/pages/bibliography.bib +++ /dev/null @@ -1,47 +0,0 @@ -% Encoding: UTF-8 - -@Standard{ocr, - title = {https://www.asam.net/index.php?eID=dumpFile&t=f&f=3950&token=21a7ae456ec0eb0f9ec3aee5bae3e8c9ebaea140[__ASAM OpenCRG__^], __1.2.0__} -} - -@Standard{osc, - title = {https://www.asam.net/index.php?eID=dumpFile&t=f&f=4908&token=ae9d9b44ab9257e817072a653b5d5e98ee0babf8[__ASAM OpenSCENARIO^], __1.2.0__} -} - -@Standard{iso3166-1, - title = {https://www.iso.org/standard/72482.html[__ISO 3166-1:2020__^], Codes for the representation of names of countries and their subdivisions, Part 1: Country code} -} - -@Standard{iso3166-2, - title = {https://www.iso.org/standard/72483.html[__ISO 3166-2:2020__^], Codes for the representation of names of countries and their subdivisions, Part 2: Country subdivision code} -} - -@Standard{iso8601, - title = {https://www.iso.org/iso-8601-date-and-time-format.html[__ISO 8601:2019__^], Date and time format} -} - -@Standard{iso8855, - title = {https://www.iso.org/standard/51180.html[__ISO 8855:2011__^], Road vehicles — Vehicle dynamics and road-holding ability, Vocabulary} -} - -@Standard{iso19111, - title = {https://www.iso.org/standard/74039.html[__ISO 19111:2019__^], Geographic information, Referencing by coordinates} -} - -@Standard{omguml, - title = {__OMG®️__, https://www.omg.org/spec/UML/2.5.1/About-UML[__Unified Modeling Language®️ (OMG UML®️)__^], __2.5.1__} -} - -@Standard{w3cxml, - title = {__W3C__, https://www.w3.org/TR/2008/REC-xml-20081126[__Extensible Markup Language (XML)__^], __1.0 (Fifth Edition)__} -} - -@Standard{w3cxmlschema, - title = {__W3C__, https://www.w3.org/TR/xmlschema-1[__XML Schema Part 1__^], __Structures Second Edition__} -} - -@misc{EPSG, - author = {EPSG.io}, - title = {https://epsg.io[Coordinate Systems Worldwide^]}, - note = {[viewed 2024-03-18]} -} diff --git a/.antora/modules/specification/pages/general_docs/abbreviations.adoc b/.antora/modules/specification/pages/general_docs/abbreviations.adoc deleted file mode 100644 index f985e7a6..00000000 --- a/.antora/modules/specification/pages/general_docs/abbreviations.adoc +++ /dev/null @@ -1,21 +0,0 @@ -[#top-abbreviations-abbreviations] -= Abbreviations - -ifndef::include-only-once[] -:root-path: ../ -include::{root-path}_config.adoc[] -endif::[] - -ASAM:: -Association for Standardization of Automation and Measuring Systems - -ECU:: -Electronic Control Unit - -UML:: -Unified Modeling Language - -XML:: -Extensible Markup Language - -> Update as needed \ No newline at end of file diff --git a/.antora/modules/specification/pages/general_docs/backward_compatibility.adoc b/.antora/modules/specification/pages/general_docs/backward_compatibility.adoc deleted file mode 100644 index 37387a04..00000000 --- a/.antora/modules/specification/pages/general_docs/backward_compatibility.adoc +++ /dev/null @@ -1,11 +0,0 @@ -[#top-backward_compatibility-backward_compatibility] -= Backward compatibility - -ifndef::include-only-once[] -:root-path: ../ -include::{root-path}_config.adoc[] -endif::[] - -{THIS_STANDARD} is backwards compatible with {THIS_STANDARD} - - diff --git a/.antora/modules/specification/pages/general_docs/foreword.adoc b/.antora/modules/specification/pages/general_docs/foreword.adoc deleted file mode 100644 index 577b323d..00000000 --- a/.antora/modules/specification/pages/general_docs/foreword.adoc +++ /dev/null @@ -1,17 +0,0 @@ -[#top-preface-foreword] -= Foreword - -ifndef::include-only-once[] -:root-path: ../ -include::{root-path}_config.adoc[] -endif::[] - -ASAM e.V. (Association for Standardization of Automation and Measuring Systems) is a non-profit organization that promotes standardization of tool chains in automotive development and testing. -Our members are international car manufacturers, suppliers, tool vendors, engineering service providers, and research institutes. -ASAM standards are developed by experts from our member companies and are based on real use cases. -ASAM is the legal owner of these standards and is responsible for their distribution and marketing. - -ASAM standards span a wide range of use cases in automotive development, test, and validation. -They define file formats, data models, protocols, and interfaces. -The standards enable easy exchange of data and tools within and across tool chains. -They are applied worldwide. diff --git a/.antora/modules/specification/pages/general_docs/introduction.adoc b/.antora/modules/specification/pages/general_docs/introduction.adoc deleted file mode 100644 index e8dfc80f..00000000 --- a/.antora/modules/specification/pages/general_docs/introduction.adoc +++ /dev/null @@ -1,79 +0,0 @@ -[#top-preface-introduction] -= Introduction - -ifndef::include-only-once[] -:root-path: ../ -include::{root-path}_config.adoc[] -endif::[] - -== Overview -Overview of {THIS_STANDARD}. - -== Conventions and notations - -[#sec-modal-verbs] -=== Modal verbs - -To ensure compliance with the {THIS_STANDARD} specification, users need to be able to distinguish between requirements, recommendations, permissions, possibilities and capabilities, and external constraints. - -The following rules for using modal verbs apply: - -[#tab-modal-verbs] -.Verbal forms for expressions of provisions -[%header, cols="20, 15, 65"] -|=== -|Provision |Verbal form |Definition -|Requirement |shall, shall not |A requirement conveys objectively verifiable criteria to be fulfilled and from which no deviation is permitted if conformance with the document is to be claimed. -|Recommendation |should, should not |A recommendation conveys a suggested possible choice or course of action deemed to be particularly suitable without necessarily mentioning or excluding others. -|Permission |may |A permission conveys consent or liberty (or opportunity) to do something. -|Possibility and capability |can, cannot |A possibility conveys expected or conceivable material, physical or causal outcome. + - A capability conveys the ability, fitness, or quality necessary to do or achieve a specified thing. -|External constraint |must |An external constraint or obligation on the user of the document, for example laws of nature or particular conditions existing in some countries or regions, that is not stated as a provision of the document. - External constraints are not requirements of the document. - They are given for the information of the user. -|=== - -[#sec-normative-and-informative-content] -=== Normative and informative content - -Content in this specification can be normative or informative. -The sections listed in <> are normative or informative per definition. -Further informative content is shown in table <>. - -[#tab-normative-informative-content] -.Normative and informative sections -[%header, cols=2*] -|=== -|Section |Indication -|Foreword |Informative -|Introduction |Informative -|Scope |Normative -|Normative references |Informative -|Terms and definitions |Normative -|Abbreviations |Normative -|Backward compatibility |Normative -|First to last specification-specific section |Normative -|Annexes |Annexes can be normative or informative. The annex heading contains the indication "(normative)" or "(informative)". -|Bibliography |Informative -|=== - -All other sections in this specification are normative. - -[#tab-informative-text-components] -.Informative text components -[%header, cols="30, 70"] -|=== -|Text components |Hints -|Notes |The document shall be usable without notes. -|Footnotes |The document shall be usable without footnotes. -|Examples |The document shall be usable without examples. -|Sequence diagrams |The document shall be usable without sequence diagrams. -|=== - -Notes, footnotes, and examples shall not contain requirements or any information considered indispensable for the use of the document, for example, instructions or permission. - -== Deliverables - -The following deliverables are provided for {THIS_STANDARD}: - -> Define the deliverables of this project here diff --git a/.antora/modules/specification/pages/general_docs/normative_references.adoc b/.antora/modules/specification/pages/general_docs/normative_references.adoc deleted file mode 100644 index 583851fb..00000000 --- a/.antora/modules/specification/pages/general_docs/normative_references.adoc +++ /dev/null @@ -1,25 +0,0 @@ -[#top-normative_references-normative_references] -= Normative references - -ifndef::include-only-once[] -:root-path: ../ -include::{root-path}_config.adoc[] -endif::[] - -The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. -For dated references, only the edition cited applies. -For undated references, the latest edition of the referenced document (including any amendments) applies. - -Standards referenced in this section are normative in such a way that parts or the whole standard shall be applied when implementing the referenced functionality. -Standards referenced in this section shall be cited normatively in the text. - -* {GLO_VAR_STA_ASAM_OpenCRG} cite:[ocr] -* ASAM OpenSCENARIO cite:[osc] -* ISO 3166-1 cite:[iso3166-1] -* ISO 3166-2 cite:[iso3166-2] -* ISO 8855 cite:[iso8855] -* ISO 8601 cite:[iso8601] -* ISO 19111 cite:[iso19111] -* OMG® UML 2.5.1 cite:[omguml] -* W3C XML cite:[w3cxml] -* W3C XML Schema cite:[w3cxmlschema] diff --git a/.antora/modules/specification/pages/general_docs/scope.adoc b/.antora/modules/specification/pages/general_docs/scope.adoc deleted file mode 100644 index bb018962..00000000 --- a/.antora/modules/specification/pages/general_docs/scope.adoc +++ /dev/null @@ -1,11 +0,0 @@ -[#top-scope-scope] -= Scope - -ifndef::include-only-once[] -:root-path: ../ -include::{root-path}_config.adoc[] -endif::[] - -{THIS_STANDARD} specifies ... - -> Define the scope of this document/standard \ No newline at end of file diff --git a/.antora/modules/specification/pages/index.adoc b/.antora/modules/specification/pages/index.adoc deleted file mode 100644 index 3029fc78..00000000 --- a/.antora/modules/specification/pages/index.adoc +++ /dev/null @@ -1,60 +0,0 @@ -[#top-this-standard] -:root-path: ./ -include::{root-path}_config.adoc[] -//NOTE: All central attributes for Asciidoctor have to be defined in the _config.adoc AND in the antora.yml in the .antora folder in root -= ASAM OpenMATERIAL -// DO NOT USE THE ATTRIBUTE {THIS_STANDARD} in the document title, it will break with Antora build pipeline! - -// DO NOT CHANGE!!! -// -:titleoffset!: -:sectnums!: - - -[IMPORTANT] -.Disclaimer -==== -This document is the copyrighted property of ASAM e.V. -In alteration to the regular https://www.asam.net/license[license terms], ASAM allows unrestricted distribution of this standard. §2 (1) of ASAM's regular https://www.asam.net/license[license terms] is therefore substituted by the following clause: "The licensor grants everyone a basic, non-exclusive and unlimited license to use the standard {THIS_STANDARD}". -==== -// -// DO NOT CHANGE!!! - - -:antora_mapping: true -ifndef::use-antora-rules[] - -[preface] -include::general_docs/foreword.adoc[leveloffset=+1] -[preface] -include::general_docs/introduction.adoc[leveloffset=+1] - -:sectnums: -include::general_docs/scope.adoc[leveloffset=+1] - -include::general_docs/normative_references.adoc[leveloffset=+1] - -include::terms_and_definitions/terms_and_definitions.adoc[leveloffset=+1] - -include::general_docs/abbreviations.adoc[leveloffset=+1] - -include::general_docs/backward_compatibility.adoc[leveloffset=+1] - -// Add further sections and chapters here as needed - -:sectnums!: -== Annexes -[appendix] -//include::annexes/REPLACE_ME.adoc[leveloffset=+2] -// Add further annexes here as needed and replace the placeholder one above - -[bibliography] -include::bibliography.adoc[leveloffset=+1] - -:sectnums!: -include::loft/list_of_figures.adoc[leveloffset=+1] - -:sectnums!: -include::loft/list_of_tables.adoc[leveloffset=+1] -endif::[] -:!antora_mapping: \ No newline at end of file diff --git a/.antora/modules/specification/pages/loft/list_of_figures.adoc b/.antora/modules/specification/pages/loft/list_of_figures.adoc deleted file mode 100644 index 6c158cfc..00000000 --- a/.antora/modules/specification/pages/loft/list_of_figures.adoc +++ /dev/null @@ -1,2 +0,0 @@ -// AUTOMATICALLY GENERATED -- DO NOT CHANGE -= List of figures \ No newline at end of file diff --git a/.antora/modules/specification/pages/loft/list_of_tables.adoc b/.antora/modules/specification/pages/loft/list_of_tables.adoc deleted file mode 100644 index 5cf30f0b..00000000 --- a/.antora/modules/specification/pages/loft/list_of_tables.adoc +++ /dev/null @@ -1,2 +0,0 @@ -// AUTOMATICALLY GENERATED -- DO NOT CHANGE -= List of tables \ No newline at end of file diff --git a/.antora/modules/specification/pages/terms_and_definitions/terms_and_definitions.adoc b/.antora/modules/specification/pages/terms_and_definitions/terms_and_definitions.adoc deleted file mode 100644 index 190beafc..00000000 --- a/.antora/modules/specification/pages/terms_and_definitions/terms_and_definitions.adoc +++ /dev/null @@ -1,12 +0,0 @@ -[#top-terms_and_definitions-terms_and_definitions] -= Terms and definitions - -ifndef::include-only-once[] -:root-path: ../ -include::{root-path}_config.adoc[] -endif::[] - -TODO: Add terms and definitions - -Static road network:: -Collection of connected roads enriched by static objects that do not change during runtime of a simulation. diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md new file mode 100644 index 00000000..2c27a961 --- /dev/null +++ b/.github/pull_request_template.md @@ -0,0 +1,23 @@ +## Describe your changes + +Add a description of the changes proposed in the pull request. + +**Some questions to ask**: + +- What is the change? +- What does it fix? +- Is this a bug fix or a feature? Does it break any existing functionality or force me to update to a new version? +- How has it been tested? + +## Issue ticket number and link + +Add a reference to a related issue. + +## Mention a member + +Add @mentions of the person or team responsible for reviewing the proposed changes. + +## Checklist before requesting a review + +- [ ] I have performed a self-review of my code/documentation. +- [ ] My changes generate no new warnings during the documentation generation. \ No newline at end of file diff --git a/content/use_cases/use_cases.adoc b/content/use_cases/use_cases.adoc new file mode 100644 index 00000000..17f92f2f --- /dev/null +++ b/content/use_cases/use_cases.adoc @@ -0,0 +1,178 @@ + + += Use Cases + +//// +Use cases in the context of ASAM standards describe the external behavior of the standardized system, that is, the interaction of the system with a user or another system. +The description of use cases is particularly useful for explaining the motivation for: + +* New standards +* Development projects for a new major version of a standard +* Development projects for adding features to a minor version of a standard + +Use cases are divided in three groups that view the standard from different perspectives. +A project proposal should consider all three perspectives in order to provide a comprehensive overview. + +* *Business use cases* describe an economic advantage, a corporate requirement, a process, a method, or an element in a larger tool chain, which involves many people within one company or across multiple companies that have a customer-supplier relationship. + +* *End user use cases* describe a requirement, process, method, or element of a tool chain that are handled by users who work with the standard. + +* *Technical use cases* describe technical requirements for the operation and interoperability of technical systems, such as tools, test systems, or application software, which the standard supports. +//// + +[cols="1,5",caption='Use case 1: '] +.Creating 3D assets +|=== +|*Type of use case* |Technical use case +|*Description* |As a content creator, I want to create 3D assets for perception sensor simulation in a standardized format. The assets shall be linked to material properties. +|*Material and 3D Structure*|Materials and 3D Structure +|*Influencing standards* |OGC CDB +|*Influencing technologies* |3D Modeling (for example, 3dsMax and Maya), 3D Engine (for example, Unreal Engine) +|*Used 3D model formats* |glTF, FBX, USD, OSG, OBJ, IVE, udatasmith, FLT, DirectX, 3DS, DAE +|*Used material formats* |MDL +|*Companies* |IAE, IPG, Foretellix, Persival, PilotD, TrianGraphics +|*Relevant user* |Content creator +|=== + +[cols="1,5",caption='Use case: 2 '] +.Creating material data +|=== +|*Type of use case* |Technical use case +|*Description* |As a measurement engineer, I want to create material data for use in perception sensor simulation. The data shall consist of physical or measured properties of materials that can be assigned to 3D meshes. +|*Material and 3D Structure*|Materials and 3D Structure +|*Influencing standards* | +|*Influencing technologies* | +|*Used 3D model formats* |glTF, FBX, USD, OSG, OBJ, IVE, udatasmith +|*Used material formats* |glTF, MDL, AFX, MaterialX, .rrdata.xml (exported from RoadRunner) +|*Companies* |Persival, PilotD +|*Relevant user* |Measurement engineer +|=== + +[cols="1,5",caption='Use case 3: '] +.Validating material properties and 3D geometries +|=== +|*Type of use case* |Technical use case +|*Description* |As a measurement engineer, I want to validate 3D geometries and material properties. This validation is performed as a comparison of the data, that is, material properties and defined points in the 3D geometry, against measurements from the real world. +|*Material and 3D Structure*|Materials and 3D Structure +|*Influencing standards* | +|*Influencing technologies* | +|*Used 3D model formats* |glTF, FBX, USD, OSG, OBJ +|*Used material formats* |glTF, MDL, AFX, MaterialX +|*Companies* |Persival +|*Relevant user* |Measurement engineer, regulator +|=== + +[cols="1,5",caption='Use case 4: '] +.Title Distributing and reusing material data and 3D assets +|=== +|*Type of use case* |Technical use case +|*Description* |As a content creation company, we want to distribute material data and 3D assets under copyright and license considerations. +To distribute material data and 3D assets efficiently, it shall be possible to reuse the data and assets in different simulation platforms and sensor models with varying sensor technologies, for example, wavelengths. +|*Material and 3D Structure*|Materials and 3D Structure +|*Influencing standards* | +|*Influencing technologies* | +|*Used 3D model formats* |glTF, FBX, USD, OSG, OBJ +|*Used material formats* | +|*Companies* |ADaC, Ansys, BMW, IPG, Fortellix, Persival, PilotD +|*Relevant user* |Content creator +|=== + +[cols="1,5",caption='Use case 5: '] +.Importing 3D assets linked to material properties between into shared sensor simulation models (FMU) +|=== +|*Type of use case* |Technical use case +|*Description* |As a sensor model developer, I want to import 3D assets that are packaged as FMUs into sensor models. +|*Material and 3D Structure*|Materials and 3D Structure +|*Influencing standards* |FMI, ASAM OSI (OSMP), ASAM OpenLABEL, ASAM OpenDRIVE, ASAM OpenSCENARIO +|*Influencing technologies* |Unreal Engine, Unity, OptiX, CUDA +|*Used 3D model formats* |glTF, FBX, USD, OSG, OBJ +|*Used material formats* | +|*Companies* |ADaC, Ansys, BMW, Persival +|*Relevant user* |Sensor model developer +|=== + +[cols="1,5",caption='Use case 6: '] +.Importing 3D assets linked to material properties into simulation platform +|=== +|*Type of use case* |Technical use case +|*Description* |As a simulation platform developer, I want to import 3D assets into a simulation platform. +|*Material and 3D Structure*|Materials and 3D Structure +|*Influencing standards* | +|*Influencing technologies* |Unreal Engine, Unity, Unigine, OptiX, CUDA +|*Used 3D model formats* |glTF, FBX, USD, OSG, OBJ +|*Used material formats* | +|*Companies* |IPG +|*Relevant user* |Simulation platform developer +|=== + +[cols="1,5",caption='Use case 7: '] +.Retrofitting or changing material properties independent of 3D assets +|=== +|*Type of use case* |Technical use case +|*Description* |As a simulation platform developer, I want to be able to add or change material properties independently of 3D assets in a simulation platform. +|*Material and 3D Structure*|Materials +|*Influencing standards* |ASAM OpenLABEL +|*Influencing technologies* |Unreal Engine, Unity, OptiX, CUDA +|*Used 3D model formats* | +|*Used material formats* | +|*Companies* |Ansys, dSPACE +|*Relevant user* |Simulation platform developer +|=== + +[cols="1,5",caption='Use case 8: '] +.Importing 3D assets with included material properties into simulation platform +|=== +|*Type of use case* |Technical use case +|*Description* |As a simulation platform developer, I want to import 3D assets with included material properties into a simulation platform. +|*Material and 3D Structure*|Materials and 3D Structure +|*Influencing standards* | +|*Influencing technologies* | +|*Used 3D model formats* |glTF, FBX, USD, OSG, OBJ +|*Used material formats* | +|*Companies* | +|*Relevant user* |Simulation platform developer +|=== + +[cols="1,5",caption='Use case 9: '] +.Moving object parts in the environment simulation +|=== +|*Type of use case* |Technical use case +|*Description* |As a simulation platform or sensor model developer, I want to move objects as well as individual parts of the objects during simulation runtime. These can be parts of a vehicle, for example, wheels and doors or the skeleton bones of a pedestrian. One option to manipulate the imported 3D assets during simulation runtime is using ASAM OSI. In the https://opensimulationinterface.github.io/osi-antora-generator/asamosi/V3.6.0/gen/structosi3_1_1GroundTruth.html[osi3::GroundTruth] message, information about moving and stationary objects is provided from the scenario engine to the sensor model. This entails object positions, orientations, velocities etc. for every simulation time step, but also a so-called model reference. This reference is the path to a 3D asset associated with the object or the stationary environment. Using the pose information together with the 3D mesh data, a 3D environment is constructed and updated for every simulation time step. Further attributes, such as https://opensimulationinterface.github.io/osi-antora-generator/asamosi/V3.6.0/gen/structosi3_1_1MovingObject_1_1VehicleAttributes_1_1WheelData.html[wheel positions] for vehicles or https://opensimulationinterface.github.io/osi-antora-generator/asamosi/V3.6.0/gen/structosi3_1_1MovingObject_1_1PedestrianAttributes_1_1Bone.html[bone poses] for pedestrians, enable a more refined movement of traffic participants in the 3D environment. +|*Material and 3D Structure*|Materials and 3D Structure +|*Influencing standards* |ASAM OSI +|*Influencing technologies* | +|*Used 3D model formats* |glTF, FBX, USD, OSG, OBJ +|*Used material formats* | +|*Companies* |Persival +|*Relevant user* |Simulation platform developer +|=== + +[cols="1,5",caption='Use case 10: '] +.Simulating energy/signal propagation with 3D assets linked to material properties +|=== +|*Type of use case* |Technical use case +|*Description* |As a simulation platform or sensor model developer, I want to simulate the energy/signal propagation using imported 3D assets with linked material properties. This is, for example, done with ray tracing. Rays are launched in a virtual 3D scene to simulate the propagation of light beams, radio waves, or ultrasonic waves. The interaction of the rays with the surfaces of the objects in the 3D environment depends on the material properties of these surfaces. These properties are assigned to the 3D geometries of the objects and imported from a material database. + +The simulation shall be able to cope with different real-time requirements, for example, SiL, HiL, open-loop, closed-loop etc. +|*Material and 3D Structure*|Materials and 3D Structure +|*Influencing standards* | +|*Influencing technologies* |Nvidia OptiX +|*Used 3D model formats* |glTF, FBX, USD, OSG, OBJ +|*Used material formats* | +|*Companies* |ADaC, Ansys, Persival, PilotD +|*Relevant user* |Simulation platform developer, sensor model developer, end user +|=== + +[cols="1,5",caption='Use case 11: '] +.Using sensor simulation to train perception algorithms +|=== +|*Type of use case* |Technical use case +|*Description* |As a perception algorithm developer, I want to use simulated environments for model training and testing, as real-world information collection is too expensive and inconvenient. +|*Material and 3D Structure*|Materials and 3D Structure +|*Influencing standards* |ASAM OSI, ASAM OpenSCENARIO, ASAM OpenDRIVE +|*Influencing technologies* |Unity, OptiX, Regeneration AI +|*Used 3D model formats* | +|*Used material formats* | +|*Companies* |Jiao Tong University, ViF +|*Relevant user* |End user +|=== \ No newline at end of file