run-operations

You optimize USD scenes by executing an op chain from inline JSON, config files, or named pipelines, writing the optimized asset to a specified output path for subsequent validation.

Applying geometry processing from validator findings involves converting recommended fixes into a runnable operation chain, executing it on the USD stage, and generating a safe, non-destructive output asset.

Long-running USD pipeline execution is supported with logging and per-operation summaries, generating a saved run log and summary JSON to track the results of the applied scene optimization operations.

Run-operations validates input paths and checks operation availability before execution, providing guardrails for correctness by prompting before destructive ops that permanently alter geometry or materials.

Destructive operations permanently alter geometry or materials, so the pipeline prompts before execution to ensure safety, though it fully supports both non-destructive and destructive pipeline configurations.

Batch processing USD assets uses named pipelines by providing the input path and pipeline name, resolving the output path, and executing the operation chain to generate optimized output artifacts with a summary JSON.