❖ NAVIGATION PLAN EXECUTION
Mission day 0 Date (UTC) - Time (UTC) 00:00:00 Status STANDBY ◀ Main page

Setup

What this page simulates: computed, input and assumed

Computed: a circular sun-synchronous orbit (period from Kepler's third law, inclination from the sun-synchronous condition, Earth rotation and Sun position from standard formulas). From it the orbits, the eclipses, the imaging opportunities (a target within half a swath of the sub-satellite point with the Sun high enough) and the ground contacts (a station sees the satellite above its minimum elevation) of every mission day.

Executed: every day the Landsat-9 physics model (sunlight/eclipse from the orbit, battery, solar wings, star trackers) is stepped in 10-minute steps and, at the start of every planned task, both controllers decide from the same state. The physics status (NOMINAL = battery above 20 % and attitude integrity above 90 %) judges each decision.

Inputs, not measurements: the target list (named places, approximate coordinates), the three example ground stations, the swath width, the two elevation masks, and the choice of what hardware each task needs:

    Limits: this is a model orbit in a Landsat-9-like plane, not the real Landsat-9 ephemeris (the orbit phase is arbitrary). Only the EPS (battery and solar wings) and star trackers A/B are physically modelled; the payload and communication nodes stay at 100 %. GPS and IMU faults are modelled as a star tracker A failure. The Kalman-filter baseline is deliberately simple (a linear filter without residual check). No hardware is involved; the maturity of the whole work is TRL 3-4.

    Ground track

    track in sunlight track in eclipse night side ground station imaging task of the day

    Kalman filter vs MetaSpace

    The day at a glance

    imaging task ground contact eclipse executed, physics nominal executed, physics critical held, physics nominal held, physics critical not reached yet

    All fault scenarios side by side

    Runs every scenario on a fresh mission (4 days, fault injected on day 2, same plan) and puts the two controllers next to each other. "Noticed after" is the simulated time from the fault until the controller reacted: MetaSpace when the mission feasibility falls below 100 %, the Kalman filter when its confidence falls below 60 % (a resolution of 10 minutes). Where the columns are equal the two controllers behaved the same; highlighted rows differ.

    Task decisions

    Orbit parameters

    Daily files

    Bio-code files written by MetaSpace each day
    Filter files written by the Kalman baseline each day