diff --git a/content/geometry/introduction.adoc b/content/geometry/introduction.adoc index 76d39644..68b9b6c2 100644 --- a/content/geometry/introduction.adoc +++ b/content/geometry/introduction.adoc @@ -2,40 +2,43 @@ == Motivation -A 3D asset refers to a digital entity that consists of a 3D geometric representation of an object and its associated attributes and metadata information. -GlTF, FBX, and USD are common 3D formats to store the geometry and visual materials of 3D models. -However, these 3D model file formats do not provide a standardized way to structure the geometry nor do they provide an extensive way to store and exchange metadata. -The ASAM OpenMATERIAL Geometry standard provides these definitions. -The OpenMATERIAL asset file (e.g. omg_my-model.xoma) contains essential information relevant to the display and interactivity attributes of the 3D model in various computer applications. -This includes metadata, material mappings and semantic information such as coordinate system and pivot point descriptions. -The actual mapping of materials is stored in a separate material mapping file (.xomm), which is linked in the asset file. -This setup allows the 3D asset to be uniformly integrated in complex simulations or real-time environments with detailed material and dynamic properties. +A 3D asset is a digital entity that includes a 3D geometric representation of an object along with its attributes and metadata. +Common formats for storing the geometry and visual materials of 3D models include glTF, FBX, and USD. -== Use-cases +However, these formats do not provide a standardized way to structure the geometry or provide extensive metadata storage and exchange capabilities. +The ASAM OpenMATERIAL standard addresses these needs. -In order to accurately replicate the real-world interaction of sensors with objects, ensuring that the behavior of sensors such as cameras, radars or lidars is correctly modeled based on the material and geometric properties of objects in the virtual environment, assets conforming to the ASAM OpenMATERIAL standards may be required in various use cases, such as +The ASAM OpenMATERIAL asset file (for example, "omg_my-model.xoma") contains essential information relevant to the display and interactivity attributes of the 3D model in various computer applications. +This includes metadata, material mappings, and semantic information like coordinate system and pivot point descriptions. +The mapping of materials is stored in a separate material mapping file (.xomm), which is linked in the asset file. +This setup ensures that the 3D asset can be consistently integrated into complex simulations or real-time environments with detailed material and dynamic properties. + + +== Use cases + +To accurately replicate how sensors interact with objects in the real world, it is essential to model the behavior of sensors like cameras, radars, and lidars based on the material and geometric properties of objects in a virtual environment. For this purpose, assets that conform to the ASAM OpenMATERIAL standards may be necessary in various scenarios, such as: + +* Accurate simulation of sensor perception: 3D assets are essential to ensure that sensors interact realistically with their environment. This includes both the visual representation, such as how objects appear and are detected by the sensor, and the material properties, like how objects reflect or absorb signals such as light or radar waves. +* Dynamic and real-time environment simulation: 3D assets with changing materials or dynamic properties, such as moving parts like wheels, are necessary to simulate environments where the interaction between sensors and objects is constantly evolving. +* Semantic labeling for machine learning applications: Assets with semantic information about sub-meshes, or labels for parts of objects, enable the system to understand and differentiate between different parts of an object, such as the wheels or windows of a car, aiding in accurate training. +* Re-using 3D assets: Using the same asset file in different simulation tools is only possible if the structure of the assets is standardized. -* Accurate simulation of sensor perception: 3D assets are required to ensure that sensors interact realistically with their environment. This includes both visual representation (how objects look and are detected by the sensor) and material properties (how objects reflect or absorb signals such as light or radar waves). -* Dynamic and real-time environment simulation: 3D assets with changing materials or dynamic properties, such as moving parts (e.g. wheels), are required to simulate environments where the interaction between sensors and objects is constantly changing. -* Semantic labelling for machine learning applications: Assets with semantic information about sub-meshes (labels for parts of objects) allow the system to understand and differentiate between different parts of an object, such as the wheels or windows of a car, which aid in accurate training. -* Re-using 3D assets: Using the same asset file in different simulation tools is only possible, if the structure of the assets is standardized. == Role of 3D exchange formats -3D exchange formats such as glTF, FBX or USD, which provide a standardized way of representing 3D models, are already widely used across industries. -In the context of OpenMATERIAL, these formats serve as the basis for seamless integration of OpenMATERIAL into existing 3D modeling and simulation workflows. -Users can continue to use their familiar tools and processes to handle geometry, while OpenMATERIAL extends these formats to enable the aforementioned use cases by adding material properties, semantic information and dynamic behaviors through additional files e.g. asset files and material mapping files. +3D exchange formats like glTF, FBX, and USD are widely used across various industries for standardized 3D model representation. + +In the context of ASAM OpenMATERIAL, these formats form the foundation for seamlessly integrating ASAM OpenMATERIAL into existing 3D modeling and simulation workflows. +Users can continue using their familiar tools and processes to manage geometry, while ASAM OpenMATERIAL extends these formats by adding material properties, semantic information, and dynamic behaviors through additional files, such as asset files and material mapping files. == Interaction with other ASAM standards -The ASAM OpenX standards aim for comprehensive, realistic and most of all exchangeable simulation data for the development and testing of autonomous systems. - -* ASAM OpenDRIVE standardizes the description of road networks. It contains some geometric definitions of the road surface, but mainly targets a semantic description of the road. -The OpenMATERIAL object class "Environment" complements this description with the possibility to define a comprehensive 3D environment that is consistent with an OpenDRIVE map. -* ASAM OpenSCENARIO is a file format designed to describe dynamic content in driving and traffic simulators, primarily focusing on complex maneuvers involving multiple entities like vehicles and pedestrians. -For both of these object classes, OpenMATERIAL defines node structures and metadata to seamlessly couple the definitions in OpenSCENARIO with a 3D model. -The 3D environment SHALL be linked in OpenSCENARIO with the https://publications.pages.asam.net/standards/ASAM_OpenSCENARIO/ASAM_OpenSCENARIO_XML/latest/generated/content/RoadNetwork.html[SceneGraphFile property]. -Individual objects, e.g. vehicles, SHALL be linked with the https://publications.pages.asam.net/standards/ASAM_OpenSCENARIO/ASAM_OpenSCENARIO_XML/latest/07_components_scenario/07_02_storyboard_entities.html#_3d_models_for_entities[model3d property]. -* ASAM Open Simulation Interface (OSI) 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, but also covering the interface for e.g. traffic participant models. -The 3D environment SHALL be linked in OSI with the https://opensimulationinterface.github.io/osi-antora-generator/asamosi/current/gen/structosi3_1_1GroundTruth.html#a83042861723a4a9e890a53aa98d88858[GroundTruth::model_reference]. -Individual objects, e.g. vehicles, SHALL be linked with the https://opensimulationinterface.github.io/osi-antora-generator/asamosi/current/gen/structosi3_1_1MovingObject.html#a07558573bee7a5fa2f0729e1cad1325f[MovingObject::model_reference] or the https://opensimulationinterface.github.io/osi-antora-generator/asamosi/current/gen/structosi3_1_1StationaryObject.html#aad1c24fcdb11699954bf3494b8632288[StationaryObject::model_reference]. +The ASAM OpenX standards strive to provide comprehensive, realistic, and most importantly, exchangeable simulation data for the development and testing of autonomous systems: + +* ASAM OpenDRIVE standardizes the description of road networks, including some geometric definitions of the road surface, but primarily focuses on the semantic description of the road. The ASAM OpenMATERIAL object class "Environment" enhances this by allowing the definition of a comprehensive 3D environment that aligns with an ASAM OpenDRIVE map. +* ASAM OpenSCENARIO is a file format created to describe dynamic content in driving and traffic simulators, with a primary focus on complex maneuvers involving multiple entities like vehicles and pedestrians. ASAM OpenMATERIAL defines node structures and metadata for these object classes to seamlessly integrate ASAM OpenSCENARIO definitions with a 3D model. +The 3D environment SHALL be linked in ASAM OpenSCENARIO using the https://publications.pages.asam.net/standards/ASAM_OpenSCENARIO/ASAM_OpenSCENARIO_XML/latest/generated/content/RoadNetwork.html[SceneGraphFile property], while +Individual objects, such as vehicles, SHALL be linked using the https://publications.pages.asam.net/standards/ASAM_OpenSCENARIO/ASAM_OpenSCENARIO_XML/latest/07_components_scenario/07_02_storyboard_entities.html#_3d_models_for_entities[model3d property]. +* ASAM Open Simulation Interface (OSI) is a specification for interfaces between models and components in a distributed simulation. OSI primarily focuses on the environmental perception of automated driving functions, but it also covers interfaces for models of traffic participants. +The 3D environment SHALL be linked in OSI using the https://opensimulationinterface.github.io/osi-antora-generator/asamosi/current/gen/structosi3_1_1GroundTruth.html#a83042861723a4a9e890a53aa98d88858[GroundTruth::model_reference]. +Individual objects, e.g. vehicles, SHALL be linked with the https://opensimulationinterface.github.io/osi-antora-generator/asamosi/current/gen/structosi3_1_1MovingObject.html#a07558573bee7a5fa2f0729e1cad1325f[MovingObject::model_reference] or the https://opensimulationinterface.github.io/osi-antora-generator/asamosi/current/gen/structosi3_1_1StationaryObject.html#aad1c24fcdb11699954bf3494b8632288[StationaryObject::model_reference]. \ No newline at end of file