Skip to content

Products

A product in Arxyne is a programme — a complete engineering context with targets, simulation history, and a USD composition stack.

Product Structure

Each product lives in products/<product>/ and contains:

products/ahmed/
├── ahmed.usda                # Root composition file
├── layers/
│   ├── design_intent.usda    # Targets, specs, req traceability
│   ├── benchmark.usda        # Competitor reference data
│   ├── prototype.usda        # Simulation results + gate status
│   ├── manufacturing.usda    # Factory config (stub)
│   └── twin.usda             # In-service data (stub)
└── simulation_runs/          # Per-run results sublayers

Targets live in design_intent.usda as arxyne:target:cd / arxyne:target:cl / etc. attributes. The requirements hierarchy is preserved as arxyne:req:* traceability attributes in the root composition file (there is no separate requirements.yaml).

The root .usda file composes all layers via subLayers. Open this file and USD resolves everything automatically.

Bundled Products

Product Type Geometry Purpose
ahmed Research body Ahmed body 25° slant Solver validation case
drivaer-notchback Sedan DrivAerML notchback Accuracy validation (aero + dynamics)
onera-m6 Wing ONERA M6 Transonic aero validation 
arxyne --list

Composition Layers

Layers have defined opinion strength (weakest → strongest):

  1. Design Intent — engineering targets, specifications, requirement traceability
  2. Benchmark — competitor reference data in the same schema
  3. Prototype — simulation and physical test results (live, updated by workflows)
  4. Manufacturing — factory configuration, BOM (stub)
  5. In-Service Twin — paired with real VIN, telemetry (stub, strongest)

Stronger layers override weaker ones where attributes overlap. All values remain queryable per-layer via USD composition queries.

Creating Products

⚠️ Coming in v0.2.0. Product scaffolding is gated behind ARXYNE_EXPERIMENTAL=1 — it creates an empty USD shell without geometry registration or solver binding. For v0.1.0, use the three bundled products directly: ahmed, drivaer-notchback, onera-m6.

The Root USD File

The root composition file declares product metadata and composes all layers:

#usda 1.0
(
    defaultPrim = "Ahmed"
    metersPerUnit = 1
    subLayers = [
        @./layers/design_intent.usda@,
        @./layers/benchmark.usda@,
        @./layers/prototype.usda@,
        @./layers/manufacturing.usda@,
        @./layers/twin.usda@
    ]
    upAxis = "Z"
)

Key attributes on the product prim (in design_intent.usda):

  • arxyne:product:reference_area_m2 — reference area for force coefficients
  • arxyne:target:cd, arxyne:target:cl — engineering targets + tolerances
  • arxyne:product:freestream_velocity_mps — default freestream speed
  • solverCaseTemplate — maps product to solver case template
  • arxyne:provenance:* — data source tracking (in prototype layer)

See Also