Runtime Loop (Populate, Read, Update)

When to Use

Use this skill when the user wants to work an ovstage scene headlessly (no renderer): load a USD scene and populate it into the runtime table, read prims back, and update the live stage. It covers the two update paths a client has once a scene is live:

1. Directly in the ovstage runtime table — write_attribute at a new ordinal (e.g. animate a prim's omni:xform transform over frames). The fast GPU-side edit; no USD round-trip.
2. Through the USD source — add_usd_reference / apply_usd_changes (or update_from_usd_time for time samples), so USD-side edits propagate into the runtime table.

Do not use it for rendering a scene (that stays in ovrtx), or for the mechanics of a single call — route those to the focused skills (application-flow, dlpack-tensor-exchange, etc.).

Inputs

Resolve inputs in this order: existing repository files and referenced snippets, explicit user request, then broader agent context.