This section provides a glossary of terms commonly used throughout Omniverse Isaac Sim.
Omniverse Nucleus offers a set of fundamental services that allow a variety of client applications, renderers, and microservices to share and modify representations of virtual worlds.
Nucleus operates under a publish/subscribe model. Subject to access controls, Omniverse clients can publish modifications to digital assets and virtual worlds to the Nucleus Database (DB) or subscribe to their changes. Changes are transmitted in real-time between connected applications. Digital assets can include geometry, lights, materials, textures and other data that describe virtual worlds and their evolution through time.
This allows a variety of Omniverse-enabled client applications ( Apps, Connectors, and others) to share and modify authoritative representations of virtual worlds.
See Nucleus Overview for a more in-depth look at Nucleus’s data model, architecture, and distribution platforms.
Omniverse Cache is a simple service that can be used both on users’ workstations as well as within infrastructure to optimize data transfers between Nucleus and it’s Clients (Apps, Connectors, and others).
See Cache Overview for more details.
Live Sync mode enables real-time “live” editing of shared files on a Nucleus Server. The Live Sync button is on the top-right corner of the Workspace.
NVIDIA Omniverse™ Kit is a toolkit for building native Omniverse applications and microservices. It is built on a base framework known as Carbonite that provides a wide variety of functionality through a set of light-weight plugins. Carbonite plugins are all authored with C interfaces for persistent ABI compatibility. A Python interpreter is provided for scripting and customization.
NVIDIA Omniverse™ Kit exposes much of its functionality through Python bindings. This provides an API that can be used to write new extensions to Omniverse Kit or new experiences for Omniverse.
For a more in-depth look at developing in Kit, see the Kit Programming Manual.
The NVIDIA Omniverse Launcher is your first step into the Omniverse. It provides immediate access to all the apps, connectors and other downloads within the Omniverse.
See Omniverse Launcher for more details.
NVIDIA Omniverse™ Create is an Omniverse app for world-building that allows users to assemble, light, simulate and render large scale scenes. It is built using NVIDIA Omniverse™ Kit. The Scene Description and in-memory model is based on Pixar’s USD. Omniverse Create takes advantage of the advanced workflows of USD like Layers, Variants, Instancing and much more.
See Create Overview for more details.
The Carbonite SDK provides the core functionality of all Omniverse apps. This is a C++ based SDK with python bindings that provides features such as plugin management, input handling, file access, asset loading and management, thread and task management, and much more.
See the Carbonite Overview docs for additional usage information.
Universal Scene Description (USD) is an easily extensible, open-source 3D scene description and file format developed by Pixar for content creation and interchange among different tools. As a result of its power and versatility, it’s being widely adopted, not only in the visual effects community, but also in architecture, design, robotics, manufacturing, and other disciplines.
Material Definition Language (MDL) is a NVIDIA-developed USD schema that represents material assignments and specifies material parameters.
See MDL Overview for more details.
A Prim is the primary container object in USD: prims can contain (and order) other prims, creating a “namespace hierarchy” on a Stage, and prims can also contain (and order) properties that hold meaningful data. Prims, along with their associated, computed indices, are the only persistent scenegraph objects that a Stage retains in memory, and the API for interacting with prims is provided by the UsdPrim class.
See the USD Glossary of Terms & Concepts for more details.
NVIDIA PhysX is a scalable multi-platform physics simulation solution. The NVIDIA Omniverse™ Physics simulation extension is powered by the NVIDIA PhysX SDK, and includes Rigid Body Simulation, Articulations, Deformable-Body Simulation, and Character Controller.
See Physics Core for more details.
The highest quality, physically accurate rendering mode.
See Render Settings for more details.
Extensions are plug-ins to Omniverse Kit that extend its capabilities. They are offered with complete source code to help developers easily create, add, and modify the tools and workflows they need to be productive. Extensions are the core building blocks of Omniverse Kit based applications.
See Extension Manager for more details.
Connectors are extensions and additional software layers on top of the open-source USD distribution that allow DCC tools and compute services to communicate easily with each other through the Omniverse Nucleus DB. Those extensions and additions are collectively known as NVIDIA Omniverse™ Connect.
See Omniverse Connect for more details.
ROS / ROS2¶
The Robot Operating System (ROS) is a set of software libraries and tools that help you build robot applications. Omniverse Isaac Sim provides many extensions, examples, and APIs for connecting to ROS and ROS2 workflows.
The NVIDIA Isaac Software Development Kit (SDK) is a developer toolbox for accelerating the development and deployment of AI-powered robots. Omniverse Isaac Sim provides many extensions, examples, and APIs for connecting to IsaacSDK workflows.
The Omniverse Stage window allows you to see all the assets in your current USD Scene. The USD Stage is the USD abstraction for a scenegraph derived from a root USD file, and all of the referenced/layered files it composes. Listed in a hierarchical (parent/child) order the Stage offers convenient access and is typically used to navigate large scenes.
The Dynamic Control extension a set of utilities to control physics objects. It provides opaque handles for different physics objects that remain valid between PhysX scene resets, which occur whenever play or stop is pressed.
See the Dynamic Control documentation for full usage examples and API details.
Riemannian Motion Policy (RMP)¶
Riemannian Motion Policy (RMP) is a set of motion generation tools that underlies most of our manipulator controls inside Omniverse Isaac Sim. It creates smooth trajectories for the robots with intelligent collision avoidance.
See the Motion Generation documentation for more details and examples.
World is the core class that enables you to interact with the simulator in an easy and modular way. It takes care of many time-related events such as adding callbacks, stepping physics, resetting the scene, adding tasks, etc. The World class is a Singleton which means only one World can exist while running Omniverse Isaac Sim. Query the World for information about the simulation from different extensions.
A world contains an instance of a Scene, think about it as a scene management class that manages the assets of interest in the USD stage. It provides an easy api to add, manipulate and inspect different USD assets in the stage as well as setting its default reset states. Many of the object classes available which could be added to a Scene usually takes an already existing USD prim in stage or creates a new USD prim, thus providing an easy way to set/ get its common properties.
The Task class in
omni.isaac.core provides a way to modularize the scene creation, information retrieval, calculating metrics and creating more complex scenes with more involved logic.
An articulated robot is a robot with rotary joints (e.g: a legged robot, a manipulator or a wheeled robot).
omni.isaac.core extension in Omniverse Isaac Sim there exists an Articulation class which enables the interaction with articulations that exists in a USD stage in an easy way.
Replicator is a Synthetic Data Generation tool for creating parameterizable offline datasets in Omniverse Isaac Sim.
See Applying and Visualizing Semantic Data for additional usage information.
Synthetic Data Generation¶
Omniverse Isaac Sim supports Synthetic Data Generations workflows. See Replicator for more details.