Validation & Reference Cases
Reference checks are visible, bounded, and traceable.
RPL Engine Workbench is checked against bounded automated reference cases for common thermochemistry, sizing, feed-system, reporting, and steady-state solve workflows. These checks support software consistency and engineering review; they are not a substitute for hardware qualification.
| Area | Reference coverage | Engineering use |
|---|---|---|
| Thermochemistry | LOX/RP-1, LOX/LH2, NTO/MMH, LOX/methane, and LOX/ethanol reference cases. | Supports review of embedded-data behavior against documented reference expectations. |
| Feed closure | Pressure-fed closure cases for representative propellant combinations. | Supports review of pressure-budget behavior across supported workflows. |
| Sizing modes | Target thrust, total mass flow, throat diameter, and injector-geometry cases. | Checks consistency across common engine setup paths. |
| Coupled solving | Steady-state coupled and fixed-inlet cases, plus fallback behavior. | Supports current steady-state review; it does not constitute transient qualification. |
| Flowfield Studio | Engineering checks, export behavior, and UI/report truth labels for supported visualization paths. | Supports design insight, comparison, and validation planning; it is not a claim of independently validated CFD. |
Engineering use
Automated reference checks are evidence of software behavior within the documented model scope. Final hardware decisions still require qualified engineering review, appropriate reference data, documented tolerances, and test evidence.
Review posture
Professional software still needs engineering review.
RPL Engine Workbench is intended to shorten design iteration and make assumptions easier to audit. Hardware decisions still require qualified review, appropriate test data, and organization-specific safety processes.
