King Air C90GT twin series-hybrid MDO over mission range × battery specific energy. Each grid cell is an independent optimization. Fig 5 minimizes fuel + MTOW/100; Fig 6 minimizes trip direct operating cost. Run end-to-end through the hangar-omd Lane B plan pipeline.
Figure 5 (fuel + MTOW/100 objective) contours over mission range and battery specific energy. Paper on the left, omd-run reproduction on the right.
Figure 6 (trip direct operating cost objective). Cost MDO has competing local minima; each cell is warm-started from the fuel-optimized design at the same grid point.
Each figure on its own for closer inspection. All cropped consistently between paper and reproduction.
Plots generated by omd-cli plot <run_id> --type all for the (500 nmi, 450 Wh/kg) headline cell. Read from the OpenMDAO recorder .sql for the converged run.
Mission, DVs, constraints, and objective match upstream openconcept/examples/HybridTwin.py (lines 372-418) with the plan-level initial-value overrides warm-starting each grid cell.
| aircraft template | kingair (C90GT) |
| architecture | twin_series_hybrid |
| num_nodes | 11 (Simpson) |
| cruise altitude | 29,000 ft |
| mission range | 500 nmi (cell) |
| climb Veas | 124 kt @ 1500 fpm |
| cruise Veas | 170 kt |
| descent Veas | 140 kt @ -600 fpm |
| payload | 1000 lb |
| battery specific energy | 450 Wh/kg (cell) |
| objective (fig 5) | mixed_objective |
| objective (fig 6) | doc_per_nmi |
| optimizer | SLSQP |
| maxiter | 150 |
| tol | 1e-6 |
| nonlinear solver | Newton (inner) |
| linear solver | DirectSolver |
| atol / rtol | 1e-10 / 1e-10 |
Every plan primitive (solver, DV bounds, constraint, objective, optimizer, result interpretation, convergence assessment) was recorded via omd-cli log-decision during interactive-builder assembly. Verbatim from plans/brelje-fuel-mdo-lane-c/decisions.yaml.
Documented trade-offs where the reproduction departs from the published result.
--warm-from fig5_grid.csv before plotting.Interactive N2 matrix of the full problem, and the discipline-level problem graph showing analysis flow between components. Both are generated during packaging; locally they may 404 until package-case-study.sh extracts the artifacts.
The provenance graph shows plan entities, decisions, run activities, and result assessments, with directed edges recording how each flowed into the next. The plan detail page renders the YAML plan with cross-links into the graph. Both are static renders of the live omd viewer.
The full pipeline is ~45 minutes wall-time on a 4-worker machine. Single cells run in under a minute.