Skip to content

Run 2 ran in orbit on 22 October 2026: result files and notes - #39

Merged
wbnns merged 1 commit into
mainfrom
opssat/run2-in-orbit
Oct 24, 2026
Merged

wbnns merged 1 commit into
mainfrom
opssat/run2-in-orbit

Conversation

@wbnns

@wbnns wbnns commented Oct 24, 2026

Copy link
Copy Markdown
Member

Run 2 (v0.4.0) ran on OPS-SAT PRETTY on 22 Oct 2026, 09:49 UTC. It matches the prediction on every point: segment 1 698 correct / 0 wrong / halt at 1,281 (event log byte-identical to the FlatSat), segment 2 fixed TMR 119 then detected, segment 3 one resume at tick 900, 1,750 correct / 0 wrong.

  • Result files: on-board run 2 and the run 2 FlatSat run under opssat/results.
  • docs/opssat.md: status, run 2 heading, new 'In orbit, 22 October 2026' section, success list.
  • README: status, In orbit table for run 2, roadmap.
  • board, qualification, security, contributing, faults.example: two runs.
  • CHANGELOG: Unreleased entry. No release.

Adds the on-board run 2 files (opssat/results/2026-10-22-ops-sat-pretty-on-board-run2)
and the run 2 FlatSat files (2026-10-21-tu-graz-flatsat-run2). docs/opssat.md gets an
'In orbit, 22 October 2026' section; README, board, qualification, security and
contributing notes say two runs; changelog under Unreleased.
@wbnns
wbnns merged commit 2968fee into main Oct 24, 2026
28 checks passed
@wbnns
wbnns deleted the opssat/run2-in-orbit branch October 24, 2026 19:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant