cae-core

Provides shared import APIs, launch flags, and inspection scripts for Kit-CAE scientific data workflows.

62|22|Updated Aug 19, 2025
One-click install
npx skills add https://github.com/NVIDIA-Omniverse/kit-cae --skill cae-core-nvidia-omniverse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cae-core
Source: https://github.com/NVIDIA-Omniverse/kit-cae/tree/main/skills/cae-core
Command: npx skills add https://github.com/NVIDIA-Omniverse/kit-cae --skill cae-core-nvidia-omniverse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires numpy, and includes scripts (resource) and references (resource) components.

What problem does it solve? Working with CAE and scientific datasets in Kit-CAE requires knowing the correct launch flags, import APIs, stage discovery patterns, and Z-up camera conventions, which are easy to get wrong and cause GPU crashes or stale renders. This Skill centralizes that shared foundation so dependent CAE skills and agents do not re-document or misapply the same primitives. ## Core Features & Use Cases - Preflight and Launch Guidance: Checklists for build validation, GPU requirements, shader cache warmup, and mandatory launch arguments that prevent ERROR_DEVICE_LOST crashes during rendering. - Unified Import and Stage Discovery: Documents the import_to_stage dispatcher for CGNS, VTK, EnSight, OpenFOAM, NPZ, and other formats, plus OmniSci dataset and field discovery patterns. - Ready-to-Run Inspection Scripts: Bundled scripts inspect CGNS/VTK files, query field statistics as JSON, and warm up the Kit shader cache, all executed through Kit's --exec environment. - Use Case: An agent needs to inspect a CGNS simulation file before visualizing it. It runs the inspect_cgns.py script via repo.sh launch, receives a JSON listing of datasets, fields, and associations, then uses the API reference to create visualization operators with correct field selections. ## Quick Start Ask the agent to inspect a CGNS or VTK file by running the bundled inspection script inside Kit-CAE with the CAE_INSPECT_FILE environment variable set to your data file.

Frequently Asked Questions about cae-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inspect a CGNS or VTK file in Kit-CAE?

Run the bundled inspect script through Kit's launcher with the CAE_INSPECT_FILE environment variable set to your file path. The script imports the file via import_to_stage and prints a JSON summary of OmniSci datasets, fields, associations, and array types between INSPECT_BEGIN and INSPECT_END markers.

How do I query field statistics like min and max for a simulation dataset?

Use the query_stats.py script with CAE_STATS_FILE pointing to your data file, optionally filtering fields with CAE_STATS_FIELDS. It outputs JSON between STATS_BEGIN and STATS_END markers containing dtype, shape, componentwise ranges, and scalar statistics for each field.

Which file formats does Kit-CAE import natively?

Kit-CAE natively imports CGNS, VTK, EnSight Gold, OpenFOAM, NPZ/NPY, EDEM, FLASH AMR, Eclipse reservoir formats (EGRID, GRDECL, INIT, UNRST), NanoVDB, and Trimesh files (STL, PLY, 3MF). All formats use the same async import_to_stage dispatcher with format-specific argument APIs.

Why does Kit-CAE crash with ERROR_DEVICE_LOST during rendering?

ERROR_DEVICE_LOST occurs when renderer settings are changed via carb.settings mid-render instead of being passed as launch arguments. Pass flags like --/app/asyncRendering=false and --/rtx/materialDb/syncLoads=true on the command line before the render starts.

Can I run Kit-CAE Python scripts with system python3?

No, every script must run inside Kit-CAE via ./repo.sh launch with the --exec flag. The host Python environment is unsupported; only Kit's environment guarantees access to numpy, pxr, omni.*, and carb modules.

What are the limitations of Kit-CAE data workflows?

Kit-CAE inspects and visualizes CAE datasets but does not modify source files. Workflows require an interactive session with a renderer, headless operation needs a virtual display, and time-varying data is supported only for formats that expose a time index.