Case Directory

This section collects the verification and validation cases. Each case includes its run provenance, conditions, results, and comparison data.

The left sidebar groups cases by physical case type (flat plate, cylinder, airfoils, …) for browsing. This page instead groups them by verification vs. validation — see below — since that distinction matters for interpreting a result but isn’t what most readers browse by first.

How Cases Are Classified

Verification and validation answer different questions, and this report keeps them apart. The test is simply what the result is compared against.

Verification Validation
Question Are the equations solved correctly? Are the correct equations solved?
Compared against Exact or analytical solutions, published results from other codes (code-to-code), grid convergence, agreement between independent schemes Experimental data, or a correlation fitted to experimental data

Two consequences worth stating explicitly:

  • The institution is not the criterion; the nature of the reference is. The Turbulent Flat-Plate Boundary Layer case uses NASA TMR material, but it is compared against CFL3D and FUN3D computations, so it is verification rather than validation.
  • Verification precedes validation. Where numerical error has not been bounded, close agreement with an experiment can be error cancellation rather than physical accuracy. Each case states what it actually established.

Within each category, cases are grouped by solver: DBNS (density-based Navier–Stokes), PBNS (pressure-based Navier–Stokes), or FR (Flux Reconstruction, high-order).

PBNS and FR are in development. Their published cases document specific verified or validated conditions; they do not establish production readiness across the broader solver paths.

Verification

DBNS

PBNS

FR

Validation

DBNS

PBNS

FR