Mars robot field guide

Mars surface robots as mobile laboratories.

Mars robots combine mobility, autonomy, landing survival, communications, power, sampling, cameras, spectrometers, drills, and thermal design into one field science system.

SojournerSpirit and OpportunityCuriosityPerseverance and Ingenuity

Mission-specific study visuals

Mars robot catalog

Open each robot for a separate engineering page with distinct project-local rover and helicopter renderings plus review notes.

Subsystem Review

What a Mars robot must survive

Entry and landing

Heat shield, parachute, radar, retrorockets, airbags, sky crane, terrain-relative navigation, and landing ellipse design.

Mobility

Rocker-bogie suspension, wheel traction, sinkage, slope safety, obstacle negotiation, and drive energy budgets.

Science payloads

Cameras, spectrometers, drills, weather sensors, ground radar, sample handling, and calibration targets.

Autonomy

Mars light-time delay requires hazard detection, route planning, fault recovery, and command sequencing.

Power and thermal

Solar or radioisotope power, battery cycling, heaters, insulation, dust effects, and night survival.

Data relay

UHF relay orbiters, direct-to-Earth backup, downlink prioritization, and compressed science products.

Mathematical model

Engineering geometry model

Engineering models are procedural, dimensionally organized teaching models. They use geometric primitives, known subsystem layout, symmetry, and transformation matrices; they are not generated from a visual image and are not exact manufacturing CAD.

Rigid transform

\[\mathbf{p}_{\mathrm{world}}=TRS\,\mathbf{p}_{\mathrm{local}}\]

Every component is positioned by translation T, rotation R, and scale S. This gives a reproducible mathematical scene graph instead of freehand drawing.

Symmetry and repetition

\[\mathbf{p}_k=R_z\!\left(\frac{2\pi k}{N}\right)\mathbf{p}_0\]

Repeated structures such as solar panels, trusses, engines, wheels, and array segments are generated by rotational or translational symmetry.

Scale verification

\[\mathrm{ratio}_{\mathrm{scene}}=\frac{\mathrm{dimension}_a}{\mathrm{dimension}_b}\]

Where the page presents relative component sizes, the scene preserves those ratios or states when readability scaling is applied.

Verification standard: the rendered object must be reproducible from stated equations, catalog parameters, or explicit geometric transforms. Visual reference images may inform presentation only; they are not the source of orbital positions, field vectors, accretion-disk gradients, timing, or engineering layout.

Limitations: browser scenes may use bounded scale, compressed distances, simplified two-body dynamics, schematic transfer curves, or educational approximations where full numerical ephemerides, CFD, finite-element models, or general-relativistic ray tracing are outside the page scope. Those simplifications are part of the model contract, not hidden image-based construction.

Open the full site-wide mathematical verification policy