Skip to main content
Ctrl+K
Assembling Digital Twins With Omniverse and OpenUSD - Home Assembling Digital Twins With Omniverse and OpenUSD - Home

Assembling Digital Twins With Omniverse and OpenUSD

  • YouTube
  • Discord
  • Survey
  • Home
Assembling Digital Twins With Omniverse and OpenUSD - Home Assembling Digital Twins With Omniverse and OpenUSD - Home

Assembling Digital Twins With Omniverse and OpenUSD

  • YouTube
  • Discord
  • Survey
  • Home

Table of Contents

Contents

  • Getting Started With Digital Twin Scene Assembly
    • Overview
    • Course Application Access
    • OpenUSD Basics
    • Asset Library Navigation
    • Open Factory Environment
    • Project Folder Structure
    • Asset Metadata Review
    • Asset Validator Troubleshooting
    • Workspace Preferences
  • Best Practices for Managing Given Assets
    • Managing Given Assets
    • Review Asset Materials
    • Centralized Materials Library
    • Replace Asset Materials
    • Assemble Production Line
    • Precision Machine Placement
    • Configuring Custom Attributes
  • Scene Optimization and Data Integration
    • Adding Props to the Stage
    • Instancing Best Practices
    • Workflow Considerations
    • Asset Inventory Export
    • Setup Navigation Waypoints
  • What’s Next

Explore Further

  • Using SimReady Assets

Resources

Physical AI Learning Hub Developer Forums Community Discord
  • Getting Started With Digital Twin Scene Assembly
  • Navigating the Provided Asset Library

Navigating the Provided Asset Library#

In this section, let’s review the assets for this project. Our asset library, in this project, is organized into two main groups: machine assets and the factory environment. Understanding this structure is an important part of preparing for digital twin scene assembly, as it helps us efficiently locate, reuse, and manage components throughout our workflow.

We will use the Script Editor extension in Omniverse to automate and streamline some asset management tasks with Python. The Script Editor lets us run code to inventory assets, validate structures, and customize our workflow.

To open the Script Editor:

  1. Navigate to Developer > Script Editor in the main menu.

    • In the Script Editor window, you can paste and modify Python scripts as needed.

Empty Script Editor with a Python tab and Run control.

Note

Replace the folder path in YOUR-PATH-HERE for your project folder.

1# Replace YOUR-PATH-HERE with the abolute path on your assets.
2import os
3asset_dir="C:/YOUR-PATH-HERE"
4
5# Walk through all subfolders and list every .usd file (case-insensitive)
6for root, dirs, files in os.walk(asset_dir):
7    for file in files:
8        if file.lower().endswith('.usd'):
9            print(f"Asset: {file}, Path: {os.path.join(root, file)}")
Script Editor showing a USD file scan and output listing asset names and paths.

Note

After running the script, we receive a list of machine assets in the following format:

For example, with asset_dir set to C:/Project/Assets:

Asset: N_03_Feeder.usd, Path: C:/Project/Assets/Machine_USD/N_03_Feeder/N_03_Feeder.usd

Path separators depend on your operating system.

This output lists .usd files; it does not validate their contents, dependencies, or readiness for use.

The provided machine assets are already in .usd format, so no format conversion is required. Inspect their metadata, dependencies, and validation results in the following lessons before assembling them.


Our Goal#

In this course, we’ll prepare these machine assets for reuse and flexible placement in multiple production line configurations. Using non-destructive methods allows us to experiment, iterate, and safely use these assets in a variety of digital twin scenarios.

previous

Understanding OpenUSD Basics

next

Open the Factory Environment

On this page
  • Our Goal
NVIDIA NVIDIA
Privacy Policy | Manage My Privacy | Do Not Sell or Share My Data | Terms of Service | Accessibility | Corporate Policies | Product Security | Contact

Copyright © 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.