domains / families / science / physical-ai-neural-reconstruction

physical-ai-neural-reconstruction

separate

Router for NVIDIA NuRec/NRE: USDZ rendering, NCore conversion, 3DGS, gRPC sensor sim, carline adaptation, PhysicalAI HF datasets. Do NOT use for SimReady or infra setup.

When to use

• Identify which upstream sibling skill answers a NuRec question.
• Locate, clone, or refresh the canonical `nurec-skills` checkout.
• Order multi-step NuRec workflows (data → conversion → train →
• SimReady packaging of CAD or source meshes → use
• Generic USD performance tuning unrelated to NuRec → use
• AKS / OSMO / NIM Operator infrastructure setup → use
• Read this skill **first** whenever a user mentions any of: `nurec`, `nurec router`, `nurec index`, `neural reconstruction`, `neural reconstruction engine`, `NRE`, `3DGUT`, `3DGRT`, `USDZ`, `NCore V4`, `sensorsim`, `sensor sim`, `novel view…

When not to use

• **Router only.** This skill never executes mutating NuRec commands.
• **Upstream-pinned.** Most recipes live in
• **Hand-curated catalogue.** A newly-added upstream sibling is not
• **Gated content.** `nvidia/PhysicalAI-*`, `nvidia/Harmonizer`, and
• **Heavy footprint.** A complete NuRec workflow can leave 150 GB+
• **NVIDIA-only stack.** Requires Linux x86_64 plus an NVIDIA GPU and
• **No Omniverse / Isaac Sim integration steps.** Handing a USDZ to
• **Not a SimReady pipeline.** NuRec produces a renderable USDZ from

Skill page

Source