Specify Behavior with SimReady#

This page expands the answer to How do I specify behavior as well as structure with SimReady?.

Two related questions are covered here:

  • If my dynamic behavior depends on attribute data, how does SimReady allow me to model the attribute data and the dynamic behavior, and provide that as a single package?

  • Another way to consider this: SimReady appears to provide the “.h” file for an object (and really just the attributes part of an object). How do I get the declaration and definition of the behaviors (the functions)?

The answer depends on the type of behavior.

Foundational Physics#

Foundational physics covers rigid body dynamics, collisions, and mass properties.

  • The simulation runtime itself provides the behavior.

  • SimReady defines the structural properties (mass, collision shapes, materials, friction) as USD schema attributes.

  • A physics engine like PhysX SDK in Omniverse Isaac Sim consumes them directly.

  • There is no separate behavioral package to author. The “function” is the physics engine, and the SimReady asset provides the “arguments.”

Domain-Specific Dynamic Behavior#

Domain-specific dynamic behavior covers electrical systems, thermal models, and fluid dynamics.

  • This is where FMI/FMU enters the picture.

  • FMI (Functional Mock-up Interface) concepts are mapped to USD as schema properties declaring simulation inputs and outputs: the “.h file.”

  • The FMU (Functional Mock-up Unit) implements the runtime behavior: the “.cpp.”

  • A SimReady asset could eventually package both together, delivering structure and behavior as a single unit.

Current State#

  • Foundational physics capabilities are the immediate focus and do not require FMI.

  • NVIDIA and partners are actively prototyping FMI/FMU-based behavioral modeling (for example, co-simulation for robotics with FMI serving multiple physics engines).

  • This is not yet part of the standard SimReady specifications.