Verification Documents
Overview
The catalog of verification manuals — run each case, confirm expected results.
TurbineX runs OpenFAST under the hood. To give that statement weight, each verification manual below is a reviewer-reproducible recipe for one well-defined analysis case on a public reference turbine: it tells you exactly how to run the case on the platform and how to confirm the result matches what the model should produce. No private datasets, no curated post-processing — what the manual shows is what the platform produces.
Available manuals
IEA-22-280-RWT-Onshore
How to run: Parametric Analysis, 24-point steady-wind sweep 3–25 m/s, TMax 300 s.
Expected result: Six-panel envelope (rotor speed, pitch, power, torque, thrust, tip deflection) is smooth and continuous, hits 22 MW at rated, and holds flat to cut-out.
IEA-22-280-RWT-Onshore (linearization-ready)
How to run: One Single Simulation per operating point with Linearize on (gravity off / rigid tower / shaft tilt 0); read the Stability + Mode Shapes tabs.
Expected result: Campbell diagram shows the expected mode order (tower pair lowest, then blade flap/edge), every mode positively damped, no resonance with a per-rev line in the operating range.
IEA-22-280-RWT-Onshore
How to run: Parametric sweep over wind speed × 6 TurbSim NTM seeds, production physics on, statistics over the stationary window.
Expected result: All seeds complete and the mean±σ load envelope follows the expected control law, saturating cleanly at rated 22 MW.
Planned manuals
The catalog grows along the same reviewer-reproducible format — one reference turbine, one workflow, one expected result:
IEA-22-280-RWT-Onshore
How to run: A DLC matrix subset (power production + parked) driven from the Certification workflow.
Expected result: Extreme and fatigue loads reproduce the reference envelope; the generated report annex matches the manual.
How the manuals fit together
- Every manual uses a public reference turbine that ships in the Turbine Library, so you can reproduce it without rebuilding a model — see Turbines.
- Manuals split into UI-driven (click-through, e.g. steady-state) and API-driven (scripted against the REST API, e.g. linearization) — pick whichever matches how you work; both reach the same result.
- Certifier-grade reports can reference the relevant manual as their model-verification annex — see Reports.