Skip to content

Note the OPS-SAT orbit run of 18 October 2026 - #7

Merged
wbnns merged 1 commit into
mainfrom
orbit-run-note
Oct 19, 2026
Merged

wbnns merged 1 commit into
mainfrom
orbit-run-note

Conversation

@wbnns

@wbnns wbnns commented Oct 19, 2026

Copy link
Copy Markdown
Member

What changed

One addition, in README.md inside "Checked against the real code", mirrored on the page in docs/index.html after the "What this does not claim" list:

  • The same quorum program (v0.3.1) ran in orbit on ESA's OPS-SAT PRETTY on 18 October 2026, three software replicas on one payload processor with faults from a schedule (results). That checks the program on a flight processor, not this model. The 1.34x comes from the 10,000 simulated missions here, not from that run, and with no real upset in its 227 s window the run calibrates nothing in this model.
  • "Those need radiation test or flight data." is now "Those need radiation test data or a much longer flight record; the 227 s OPS-SAT run of 18 October 2026 saw no real upset."

No data-k strings and no data.json changes.

Checks

  • cargo fmt --check: pass
  • cargo clippy --all-targets -- -D warnings: pass
  • cargo test --release: 30 passed, 0 failed
  • ./scripts/check-readme.sh --run: ok (36 display strings checked)

… real code"

The same quorum program (v0.3.1) ran in orbit on ESA's OPS-SAT PRETTY. That
checks the program on a flight processor, not this model; the 1.34x comes
from the 10,000 simulated missions, and with no real upset in the 227 s
window the run calibrates nothing. Same paragraph on the page after "What
this does not claim". No data-k strings or data.json changed.
@wbnns
wbnns merged commit 404d337 into main Oct 19, 2026
2 checks passed
@wbnns
wbnns deleted the orbit-run-note branch October 19, 2026 15:18
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