Open Source Robotics

A curated collection of high-quality open source robotics projects, tools, and software to propel the robotics community forward.

USD

  • Also called: Universal Scene Description, OpenUSD, Pixar USD
  • Category: Software & tooling › Tools & formats
  • Tags: robot-description, simulation, file-format

Open scene description format from Pixar that Isaac Sim and other simulators use to describe robots, environments and their physics as layered files.

Definition

Universal Scene Description is an open framework for describing 3D scenes, created at Pixar for film production and released as open source in 2016. A USD stage is a hierarchy of prims, each carrying typed properties, and it can be assembled from many files: sublayers stack edits on top of each other, references and payloads pull in other assets, and variant sets switch between alternatives such as two grippers on the same arm. Files come as readable text (.usda), compact binary (.usdc) or a zipped package (.usdz).

Robotics took it up because simulation for robot learning needs whole worlds, not single robots. NVIDIA built Isaac Sim and Omniverse on USD, so a robot, its sensors, the warehouse it works in and the props it handles all live in one stage. The UsdPhysics schema adds rigid bodies, collision shapes, mass properties, joints and articulations, which is what turns a rendered model into something a physics engine can step. Robots described in URDF or MJCF are usually converted into USD on import rather than written in it by hand.

The composition system is the part that matters most in practice. Several people can work on one scene without overwriting each other, and a randomised training scene can swap textures, lighting or object placement by changing a layer rather than copying files. The cost is complexity: USD is far larger than URDF, its robot-specific conventions are still settling, and the same robot can look different depending on which tool wrote the file.

The Alliance for OpenUSD, formed in 2023 by Pixar, Adobe, Apple, Autodesk and NVIDIA, now works on standardising it. The code is published under the Tomorrow Open Source Technology License, which is the Apache License 2.0 with a different trademark section.

Why it matters

USD is how a growing share of robot simulation describes the world a robot works in, not only the robot itself. It matters because large-scale robot learning depends on many varied scenes, and USD's layers let a team build one environment, vary it programmatically and share it without copying files. Anyone moving a robot into Isaac Sim, or using simulation-ready asset libraries, will meet it, usually after converting a URDF or MJCF model into it.

Key applications

  • Describing robots, sensors and environments in Isaac Sim and Omniverse
  • Building simulation-ready asset libraries that many projects can reuse
  • Randomising scenes for synthetic data and robot learning without copying files
  • Digital twins of factories and warehouses that combine CAD, robots and layout
  • Exchanging 3D scenes between CAD, rendering and simulation tools

In practice

Most robotics teams do not write USD by hand. They export the robot from CAD or convert an existing URDF or MJCF file with a simulator's importer, then check the result: joint axes, limits, collision shapes and mass properties are where conversions usually go wrong. Environments are assembled from referenced assets, and training variations are applied as separate layers so the base scene stays untouched. Text .usda files are useful for reading and diffing, binary .usdc files for anything large.

Common misconceptions

  • USD replaces URDF: in practice URDF and MJCF are still how most robots are first described, and USD is often what they are converted into for simulation
  • A USD file is a single file: a stage is usually composed from many layers and referenced assets, and moving one file without the others breaks it
  • Converting a robot into USD preserves its physics automatically: joint limits, drives, collision shapes and inertia often need checking after import
  • USD is an NVIDIA format: it was created at Pixar and is now standardised by the Alliance for OpenUSD

Who should know this

  • Anyone bringing a robot into Isaac Sim or another USD-based simulator
  • Engineers building simulation environments or digital twins
  • Researchers generating synthetic training data with randomised scenes
  • Developers converting robot models between URDF, MJCF and USD

Related technologies

  • URDF
  • MJCF
  • NVIDIA Isaac Sim
  • NVIDIA Omniverse
  • UsdPhysics schema
  • glTF
  • SimReady assets

Related terms

  • URDF
  • Digital Twin
  • Sim2Real
  • Domain Randomization

Related projects

  • GENESIS: World's fastest physics engine: 43M FPS for embodied AI learning
  • LeRobot: HuggingFace ML library for real-world robotics in PyTorch
  • text-to-cad: Lets AI coding agents design parts in Python CAD and export robots to MuJoCo
  • SolidCraft: Open-source parametric 3D CAD in Rust that exports robot assemblies to URDF
  • PyBullet: Python physics simulator for robotics and RL research with fast CPU-based simulation
  • Newton: Open GPU physics engine for robot learning, with Kamino for closed-loop linkages

Videos

  • Five Things to Know About USD | NVIDIA Omniverse Tutorials: NVIDIA
  • Import Your Robots From URDF to USD - Isaac Sim Tutorial: LycheeAI

Wikipedia

  • Universal Scene Description

This website requires JavaScript to function properly. Please enable JavaScript to explore our collection of open source robotics projects.