IASTAM 6.0 · Track 1 · Problem 2

Every frame has a cost. Make it count.

Onboard AI that measures its hardware, then adapts to the mission.

How it works
Mission twin · Tunis ground pass Simulated
Balance between missed deadlines and expected accuracy 64missed 90.7 %accuracy

Without cost feedback

64missed deadlines

expected accuracy 90.7 %

MIZAN, cost feedback on

?missed deadlines

Switch on MIZAN to compare

The trade: 52 fewer missed deadlines for 0.6 points of expected accuracy (90.7 % to 90.1 %).

Recorded simulation result, not flight data. Replays two recorded runs of the mission twin; it does not execute the controller.

01 · The idea

A satellite cannot trust a cost sheet written on a laptop.

A satellite that runs AI onboard must decide, frame by frame, how much of a small and shifting energy, memory and time budget each inference deserves.

MIZAN (ميزان, Arabic for balance) weighs accuracy against the energy and time it costs, using costs measured on the board it runs on, and keeps correcting them while it flies. Its safety filter can refuse a configuration but never chooses one.

Three choices per frame

Model depth
Exit early from a MobileNetV3-Small network when it is confident; go deeper when it is not.
Frame frequency
Run or skip a frame, weighed by its value: clear land is worth more than cloud, ocean or night.
Input quality
Process the image at 48 or 64 pixels.

How MIZAN decides, every frame

  1. 1

    Observe state

    Battery, temperature, deadline, memory and the value of the frame.

  2. 2

    Propose configuration

    The most valuable option the energy price allows, from the corrected menu.

  3. 3

    Safety veto

    Refuse anything whose bound breaks the deadline, battery or heat limit. It can veto; it never chooses.

  4. 4

    Execute

    Run the chosen exit and resolution on the board, or skip the frame.

  5. 5

    Measure actual cost

    Time what the board really took.

  6. 6

    Update the cost menu

    Fold measured over predicted into a conformal latency bound for the next frame.

02 · Results

On the board, measuring buys deadline safety.

Measured Simulated

Measured · Raspberry Pi 4B

−49 %missed deadlines

−31 %mean latency

After online cost correction, on the target board. The controller stopped trusting the laptop menu and spread its choices across seven options instead of one.

Deadline misses of 720 frames per arm
45feedback off
23feedback on
0cheapest fixed option
Mean latency ms
26.72feedback off
18.42feedback on
12.37cheapest fixed option
Expected accuracy menu value, %
90.65feedback off
87.94feedback on
86.45cheapest fixed option
Conditions
Pi 4B, synthetic frames, 720 per arm, interleaved; p = 0.0065 (misses), p = 0.0011 (latency)
Limit
The cheapest fixed option still missed none
Source
Paper, Section IV-G
Measured · Raspberry Pi 4B

6.5× optimistic

A cost menu profiled on a development laptop underestimates what the payload board takes, floor to floor.

Conditions
Fastest quarter (p25), two sessions: 6.56× and 6.50×
Source
Paper, Section IV-F
Measured · data-centre GPUs, not the payload

52–57 % less energy per inference

Adaptive routing against full depth, at 64 px, with idle draw included, while the accelerator is saturated. Paced at 10 frames/s, the saving disappears.

Energy per inference, full depth against adaptive, saturated
GPUFull depthAdaptiveSaved, saturatedAt 10 fps
A40324.4 mJ151.5 mJ53.3 %not run
L4157.2 mJ67.7 mJ56.9 %0.65 %
T4157.8 mJ75.8 mJ52.0 %−0.05 %
Conditions
Saturated GPUs; not measured on the satellite payload
Source
Paper, Section IV-B, Table III

03 · Demo

Every frame has a deadline. Watch MIZAN keep it.

Download MP4

A four-minute narrated demo. A simulated 3U CubeSat has 40 ms per frame. Over a ground station the downlink slows inference 2.4×, then come heat and an eclipse with one solar wing stuck. The repository's own controller decides every frame, with and without cost feedback. Then the whole system runs live on the board, 1,440 frames per arm, and is killed mid-mission and recovers. Orbit sequences are simulations; board numbers are measured on a Raspberry Pi 4B.

This run's log Simulated
ControllerMissedMean latencyExp. accuracy
MIZAN1220.2 ms90.1 %
Menu-trusting6422.0 ms90.7 %
Static, richest8820.9 ms90.7 %
Static, cheapest012.9 ms86.4 %

04 · Poster

The A2 poster, explorable.

100 %
The MIZAN A2 poster: header with title and authors, then sections 01 to 08 in two columns, from context and problem to references and a QR code.

05 · Paper

MIZAN: Measure-First Adaptive Inference for Energy-Constrained Satellite Payloads

Ahmed Hedhili, Salem Essid, Ahmed Mnasri · IASTAM 6.0

We test the three levers an adaptive inference system has on a satellite: which model to run, how often to run it, and how much detail to process.

The model lever saves 52–57 % of energy per inference only on saturated accelerators. A laptop-profiled menu is 6.5× optimistic on the Raspberry Pi 4B, and correcting it online cuts missed deadlines by 49 % on the board. Live on the board, the full system held its latency bound. In a pre-registered held-out evaluation over laptop costs it caused no breach in 100 simulated runs, though at the board’s costs only with a battery reserve added afterwards, and it lost quality under heat; a step-down rule written afterwards beats every single fixed option in simulation (94.3 % against 92.3 %).

Cite this work

@misc{mizan,
  title  = {{MIZAN}: Measure-First Adaptive Inference for
            Energy-Constrained Satellite Payloads},
  authors = {Ahmed Hedhili, Salem Essid,  Ahmed Mnasri},
  note   = {IASTAM 6.0 Technical Challenge, Track 1, Problem 2.
            Team INTERSTELLAR, SUP'COM, University of Carthage},
  year   = {2026}
}

Supporting materials

  • PosterA2 PDF, 1.4 MB
  • Demo videoMP4, 3:49, 64 MB
  • Code and claim checkerComing with the final submission

06 · Team INTERSTELLAR

The people behind MIZAN.

École Supérieure des Communications de Tunis (SUP'COM), University of Carthage, Tunisia.