# Design This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold. ## World Origin at the lower left. Pad A is a 8 m wide flat at z = 0, from x = 28 to 36. Terrain otherwise follows `fixtures/lander-terrain.json`. ## Ballistic drop Start x = 32, z = 30, velocity 0, thrusters off, atmosphere off. After 2 s, z = 30 - 0.5 * gravity * 4. At default gravity 1.62, z = 23.52 m. Tolerance 0.05 m. ## Residuals Rest-state, 60 steps, no injection: the L2 of velocity increment per step, mean over the last 10 steps, is under 1e-4 for `stable-fluids` and under 5e-4 for `lattice-boltzmann`. Closed-box mass (atmosphere on, no craft) stays within 1% of the start. ## Tapes The two fixture files are the authority for poses and for the pass/fail result. Goldens are 1600 by 1000, tolerance 8 levels, 98% of pixels (the plume may use a 12-level tolerance in the overlay region defined in `fixtures/plume-mask.png`). ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `gravity` | Gravity, m/s² | 1.62 | A positive number. The default is a small moon. | | `fuel` | Fuel mass, kg | 80 | From 20 to 200. The lander dry mass is 200 kg. | | `atmosphere` | Thin atmosphere | on | A background fluid field the exhaust pushes through. If off, exhaust still exists as a jet into vacuum. | | `plume` | Draw the plume | on | The fluid field is visible as a density overlay. | | `solver` | Solver | stable-fluids | Two ways to step the field. Both must pass the same residual checks within their tolerances. | ## Acceptance at the defaults The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins. | Fixture | Role | | --- | --- | | `design.md` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/lander-crash.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/lander-soft.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/lander-terrain.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `spekkr.inputs.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy. ## Screenshots These pictures are headless-Chrome captures of the working reference in `reference/preview.html`, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel. | File | What it shows | | --- | --- | | `shots/approach.png` | The lander at 142 m, exhaust in the CFD field, the pad below. | ## How to verify 1. Run the checks at the default inputs, without a network. 2. Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file. 3. Repeat once at the person's inputs when they differ from the defaults. 4. A deterministic landing fixture and a crash fixture, both at a fixed timestep, produce the documented poses and outcomes. The fluid field has a residual check and a closed-box mass check for both solvers. Golden frames cover approach, plume, landing and crash. No physical tunnel and no network.