Rotating detonation engine Project atlas
One demonstrator. Six parallel workstreams. Evidence before release.
Stationary, instrumented research hardware; establish repeatable rotating-detonation operation.
Click a task, gate or recovery card for details. Select a hollow decision to trace what it unlocks. Keyboard: Tab to items; Enter/Space opens; arrow keys move between tasks; Escape closes details. Scroll horizontally on smaller screens.
01 / Parallel, not premature
CAD, controls, data tools and facility work start early. Use shared interfaces + provisional load ranges; release reviewed packages in stages.
02 / Release is conditional
CFD does not certify hardware safety. Pressure-containing and combustion-critical fabrication stays behind G2 reviews.
03 / Recovery is controlled
A failure changes the baseline, not the evidence standard. Re-enter a named gate; re-review and re-authorise where affected.
Accessible task register / all draft owners, inputs, deliverables, dependencies and acceptance criteria
All task-level execution criteria and detailed timing are ASSUMPTIONS for institutional review. No task or validation is represented as completed.
| Task / owner / window | Inputs | Deliverable | Dependency | Acceptance (draft) |
|---|
Inside the demonstrator
Head end to exhaust. Generic component relationships, not a selected engine configuration. Numbered parts link to owners, gates, evidence and recovery loops.
Schematic / not to scale. Transparent walls reveal relationships; spacing is illustrative. TBD: set by reviewed design. No flow passages, injector geometry or fabrication detail are represented.
Part / owning workstream / release gate
The wave rotates. The hardware does not.
A synchronized annulus and an unrolled periodic strip show one illustrative wave, replenishment near the head end and downstream product flow. Display speed is arbitrary, not physical time.
A shock-coupled reaction consumes fresh mixture locally.
Products expand downstream; local injection can be suppressed.
Fresh mixture re-enters as local conditions permit.
The next passage needs a suitable fresh layer.
What combines into credible evidence
Synchronized, high-bandwidth circumferential pressure measurements support propagation direction, wave count and speed.
Time-resolved optical diagnostics, where feasible, can help distinguish the shock and reaction structure. Combine these with mixture-specific detonation references, uncertainty and repeatability.
Supply/flow records, thermal measurements and as-built configuration establish context; calibrated thrust measurements support performance claims, not detonation identification by themselves.
What does not establish it
Glow, noise, a single oscillating pressure signal or a pleasing animation are not sufficient proof of rotating detonation.
Speed near an ideal reference is supporting evidence, not a stand-alone certificate. CFD agreement alone cannot establish an experimental wave mode.
No data exists in this illustration. Actual evidence and acceptance must be reviewed; a negative demonstration result remains valid.
Couplings, uncertainty and release conditions
All component assessments and acceptance wording are draft assumptions. The map is a relative discussion aid, not a quantified risk score.
Dashed placements express provisional judgement. Lower relative uncertainty does not mean low risk or design readiness. Click a marker for its full card.
Break down. Review. Come back.
Scenario controls link risks to hardware and the project timeline. Revision stamps are a reversible demonstration of change control, not actual fabrication history or approval.
Models inform hardware. Experiments challenge models.
Each stage supplies bounded evidence, not safety certification. Hollow markers mean not yet validated; no stage has been completed in this project record.