Omniverse Glossary of Terms
- Action Graph
An Action Graph is an OmniGraph that triggers actions in response to a particular event.
A mode of USD authoring where the USD authoring layer is automated. The edits made to a given prim will be automatically applied to the USD layer they originated in. This removes the need for the user to manually set an USD authoring layer.
One of the reference lines of a coordinate system typically referred to as X, Y and Z.
Curve primitives based on the UsdGeomBasisCurves API. These curves have a
basisproperty, which defines how to interpolate the vertices of cubic curves.
- Compute Graph
“Compute graph” is a synonym for OmniGraph, an engine for programmatically manipulating scenes with a graph-based visual scripting interface.
Nucleus 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).
Immutable historical file versions. Checkpoints are used for version control and allow you to look at and restore the stage to a previous state.
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.
A mode of USD authoring where a user must manually choose the USD authoring layer.
Asset inside a USD scene that is used to configure the properties of a particle effect, such as emission rate and color.
Endpoints are the path/location under which the API is exposed. Omniverse Kit does not impose a type of API so users are able to build fully REST based APIs or Interactive, RPC etc. ones. The specification for the API is generated and uses OpenAPI. It can be thought of as the path section of a URL.
An extension is a uniquely named and versioned package loaded at runtime. Extensions are are powerful plugins that can be used to extend the functionality of existing apps such as Create, View and Machinima
By default services are stateless, this is something that is critical for services to be distributed and scalable. However, certain objects like DB connections, configuration, task queues are generally stateful and for speed, efficiency can be reused. To do this, facilities are added. They are registered with routers on startup and can be injected into the services that need them. This also allows componentization making it possible to change how services are running depending on the environment they are running in by simply changing out one facility for another. For example a configuration facility can be a simple python dictionary during unit tests or a more advanced configuration file for production use. All that would need to change is the facility that gets registered with the router.
- Ground Truth
Omniverse Isaac Sim can be used to generate ground truth data that is very similar to real-life analogs.
Refer to Replicator for more details.
- Isaac Sim
A robotics simulation toolkit for NVIDIA Omniverse™.
Refer to our Isaac Sim overview for details.
A light-weight and less manipulable copy of a prim.
The act of a user being added to a named session.
The toolkit and framework for building custom apps in Omniverse.
A component of the collaborative nature of USD. Each layer in USD signifies a user’s “opinion” on assets inside a stage. Layers can override other layers.
The act of a user exiting a named session.
- Live Layer
A specialized file which holds the collaboration edits of a Live Session. These have an extension of .live. They are generally placed automatically in the USD Session Layer of a stage.
- Live Session
A named activity where multi users in multiple Omniverse connected applications and/or connectors can collaborate on a file together.
- Live Session End
The act of ending a named session. This communicates to all users that the session is ending and all users must stop working.
- Live Session Start
The act of joining or creating a new named session.
- Live Sync
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.
Materials are assets that are assigned to a 3D model. They describe how an object looks and responds to lighting. In Omniverse, most materials are based on physically based rendering, which means they support properties like Albedo, Roughness, Metallic, Transparency and others.
An open-source material definition language developed by NVIDIA
The act of combining single or multiple source Layers into target layer(s). Most common usage is to merge a stronger layer to a single target layer beneath it.
A mesh is a subdividable primitive that consists of points, edges, and faces that define its shape. In USD, a mesh is encoded in a UseGeomMesh class.
- Multi-user collaboration
Omniverse is built on USD, a collaborative technology that allows 3D artists to build together. Collaboration is at the heart of all Omniverse apps and users are able to collaborate on USD scenes in real-time.
A nit is a unit of measure of light intensity, equal to one candela per square meter.
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.
An engine for programmatically manipulating scenes with a graph-based visual scripting interface.
This is the leader of a given Live Session. The user who creates the session is the owner by default.
A panel is a user interface (UI) element within Omniverse Applications that contains other UI elements. You can often dock a panel into a position within a window, and you typically access panels with tabs.
Here’s an example of the Stage panel in Omniverse USD Composer:
Users that have joined a Live Session
- Particles Editor
Extension that is used to manage the nodes of a particle effect
A payload is a USD layer operation that you use to point from one prim to another, like a reference. The key difference between payloads and references is that payloads are not always consumed when a stage is built. Payloads are weaker than references, and if you decide not to load them, they’ll will be recorded, but not consumed.
- Push Graph
A Push Graph is an OmniGraph that evaluates every node on every frame. It is convenient to use, but inefficient.
Short for “primitive”, the prim is the fundamental unit in Omniverse. Anything imported or created in a USD scene is a prim. This includes, cameras, sounds, lights, meshes, and more. Primitives are technically containers of metadata, properties, and other prims. Read more about USD prims in the official documentation.
A reference is a USD layer operation that you use to point from one prim to another. In doing so, you can compose a scene description, called a namespace, from smaller components. Within the namespace, referenced prims have their own, unique names. When you load a scene, referenced USD files are opened only once, even if they are used multiple times in the namespace. Finally, when a stage is built, references are always consumed. This is a key distinction between references and payloads.
Also termed image synthesis is the process of generating a photorealistic or non-photorealistic image from a 2D or 3D model by means of a computer program.
Replicator is a Synthetic Data Generation tool for creating parameterizable offline datasets in Omniverse Isaac Sim.
Routers, although not required, allow the grouping and management of multiple endpoints. This becomes increasingly important and useful as services grow. It simplifies the organization and management of services creating a logical object under which endpoints are combined. They also allow the registration of facility type objects.
Routers are available from:
A Shape is a geometric primitive that maps to one of USD’s five “intrinsic”
Shapes are not meshes, in that they are not defined by a collection of points, edges, and faces. Instead, they are defined by their shape and volume.
Pixar describes their use cases for these prims in their UsdGeomGprim schema documentation.
- Session Layer
A USD feature for in memory and temporary USD layers. These do not persist or save with the main USD stage. The Live Layers generally exist here.
- Services core
omni.services.core is, as it name indicates, the extension that sits at the core of the services framework.
It uses several different components to form a framework. When services are ready they are registered with this extension that will make sure they are mounted within the application and accessible via a transport.
This is available from:
The Omniverse Stage panel allows you to see all the assets in your current USD Scene. The 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.
- Synthetic Data Generation
Omniverse Isaac Sim supports Synthetic Data Generations workflows.
Refer to Replicator for more details.
A user interface element that you use to reveal and organize panels.
The core of the services framework is transport agnostic. This means that by just enabling omni.services.core and registering services they could only be used by an in memory transport.
To make these services accessible from outside of Omniverse Kit or between Omniverse Kit instances different transports can be used. Transports can be mixed and matched and the only limitation would be the port the transports would be listening on.
Transports, bundled with Omniverse Kit, are found underneath omni.services.transports but additional transports can be added. They would need to inherit from omni.services.transport.server.base.BaseTransport. It will need to implement a way to translate the incoming requests so it can be passed to omni.services.core.
Universal Scene Description (USD) is the fundamental representation for assets in Omniverse.
A window is a user interface container that presents an entire application.
The Transform (Xform) is the fundamental element of all objects in Omniverse, the Location.
An XForm can also be created, in this case it is the simplest of all prims and acts as a locator.
The axis of orientation of a given scene/prim. Y-Up refers to the Positive Y Axis is pointing up. This orientation setting is generally set by the application of the scene/prims origination.
A reference to the axis of orientation of a given scene/prim. Z-Up refers to the Positive Z Axis is pointing up. This orientation setting is generally set by the application of the scene/prims origination.