Model notes

What the Mission Design simulation computes, what it simplifies, and which numbers come from NASA pages. Everything in src/md_model.js is described here. The game is a teaching model: its numbers are not data for any real spacecraft or rocket.

1. Values from NASA pages

Opened on 2026-11-15. These are the only numbers in the game text that we took from an agency page.

ValueSourceWhere the game uses it
NASA's Aqua satellite takes about 99 minutes to orbit the Earth at about 705 km, in a sun-synchronous orbit that keeps the angle of sunlight on the ground as consistent as possible.NASA Earth Observatory, Catalog of Earth Satellite OrbitsText of the sun-synchronous orbit card. The game's orbit altitude (600 km) and eclipse time are game values chosen to be similar, not copied.
A polar orbit moves the satellite from pole to pole, about 99 minutes for one orbit (for that example), inclination 90 degrees.same pageText of the polar orbit card.
Geostationary orbit: 42,164 km from the centre of the Earth, about 36,000 km above the surface.same pageNot selectable in the game; used in the explanation that higher orbits need more launch energy.
Moon distance: mean 384.4 thousand km, perigee 363.3, apogee 405.5 thousand km.NASA NSSDC Moon Fact SheetText of the lunar orbit card (long link distance).

Not confirmed from a NASA page, so not claimed as sourced: CubeSat unit size and mass limits (sources disagree on the 1U mass limit), launcher capacity and cost figures, radio rates, instrument figures. Those are game values.

2. What the simulation computes

Mass. The total mass must not exceed the launcher's capacity to the chosen orbit (capacity is zero for orbits a launcher cannot reach).

mcraft=∑imi≤mcap(launcher, orbit)

Power. Average power from the panels depends on panel area A, a wing multiplier k, a fixed peak flux and the share of the orbit in sunlight fsun. It must cover the average load.

Pgen=A·k·190·fsun≥Pload=3+∑ipidi+ptxfcontact+0.05pprop

Units: watts and square metres. The constant 190 W per square metre and the 3 W core load are game values. di is the duty cycle of instrument i.

Battery through eclipse. During eclipse the battery supplies the load; the design is rejected if more than 80 percent of the battery would be used each orbit.

Pload·teclipse/60Cbattery≤0.8

Eclipse time teclipse is in minutes, battery capacity Cbattery in watt-hours.

Data and communications. Data produced per day, and what the radio can send during ground-station contact:

G=∑igidiD=R·tcontact·608·1000ρ=min(1,DG)

R in megabits per second, tcontact in minutes per day, G and D in gigabytes per day. Data beyond the bus storage is lost.

Budget and time. Hardware, launch and ground cost are added and compared with the scenario budget (scaled by difficulty). Weeks to launch are the sum of build weeks and the launcher's wait, compared with the launch window.

Science. Instruments of the kind the scenario wants count in full, other kinds one third. The orbit multiplies everything by how useful it is for the objective.

S=forbit∑isidiwi

wi is 1 for a matching instrument and 0.3 otherwise.

Delta-v (background). The rocket equation links the speed change a thruster can give to its propellant. The game does not compute it: each thruster has a fixed delta-v and the Moon scenario needs a minimum.

Δv=Isp·g0·ln(m0mf)

3. Random events

A seeded random generator rolls each day. The same seed gives the same mission, so a replay is exact. Events: solar flare (panel output drops for 3 days), ground-station outage (no downlink for 2 days), instrument glitch (no measurements for 2 days), one wing opening only halfway (at launch), and launch failure (depends on the rocket's reliability). Chances are scaled by difficulty.

4. Score (100 points)

Mission performance30Success gives full points; partial success and near misses give some.
Science value20Science returned divided by the target.
Resource efficiency20Using 60 to 100 percent of budget, mass and time limits scores best; going over scores zero; wasting most of a limit scores less.
Decision quality15Margins on the scenario's critical resources, and few warnings.
Teamwork15Share of the four roles whose goal the final design meets.

5. Simplifications, stated plainly

Back to the game