diff --git a/src/data/claims.json b/src/data/claims.json index b873600..7f2ea84 100644 --- a/src/data/claims.json +++ b/src/data/claims.json @@ -4,7 +4,7 @@ "sources": { "flight": { "repo": "mruspace/flight", - "commit": "215547b", + "commit": "bbdad54", "bench": ["2026-10-11-darwin-arm64.json", "2026-10-11-linux-aarch64.json", "2026-10-11-linux-x86_64.json"], "bench_commits": { "darwin-arm64": "7c1a629", "linux-aarch64": "d79b345", "linux-x86_64": "d79b345" }, "kat": "2026-10-11-darwin-arm64-kat.json", @@ -805,13 +805,13 @@ "text": "5" }, "flight.fprime.unit_tests": { - "value": 44, + "value": 45, "format": "int", "unit": "F´ unit tests", "scope": "fprime/Mru components, fprime-util check in CI", - "conditions": "HealthRegistry 5, ReplicaHost 5, FaultInjector 8, RedundancyManager 23, RunRecorder 3", + "conditions": "HealthRegistry 5, ReplicaHost 5, FaultInjector 8, RedundancyManager 23, RunRecorder 4", "source": { "repo": "flight", "kind": "manual", "ref": "docs/fprime-design-fpp.md" }, - "text": "44" + "text": "45" }, "flight.kani.core": { "value": 4, diff --git a/src/pages/concepts/architecture.astro b/src/pages/concepts/architecture.astro index 215bf14..b8a3fee 100644 --- a/src/pages/concepts/architecture.astro +++ b/src/pages/concepts/architecture.astro @@ -105,7 +105,7 @@ const crumbs = [
MruOpsSat)
run full length in ESA's OPS-SAT experiment environment under emulation,{' '}
bench on general-purpose processors, Dusk, and the quorum demo on the SEPP
@@ -271,7 +271,7 @@ const crumbs = [
RedundancyManager,{' '}
- HealthRegistry and ReplicaHost are built and tested: 44 unit tests with the two
+ HealthRegistry and ReplicaHost are built and tested: 45 unit tests with the two
test-only components, a system test against the demo's counts on the bench schedules, and a first F´
deployment. They have not run on flight hardware. The quorum demo, without F´,{' '}
ran in orbit on ESA's OPS-SAT PRETTY satellite on 18 Oct 2026
diff --git a/src/pages/concepts/qualification.astro b/src/pages/concepts/qualification.astro
index b2234eb..82b2ad5 100644
--- a/src/pages/concepts/qualification.astro
+++ b/src/pages/concepts/qualification.astro
@@ -121,7 +121,7 @@ const crumbs = [
- Status as of 22 Oct 2026, flight v0.6.0. The F´ components, the deployment and the C interface have numbered + Status as of 22 Oct 2026, flight v0.7.0. The F´ components, the deployment and the C interface have numbered requirements, each with a verification method, but no trace to mission or standard requirements.
diff --git a/src/pages/core/fprime.astro b/src/pages/core/fprime.astro index 2e5fc9a..a21a687 100644 --- a/src/pages/core/fprime.astro +++ b/src/pages/core/fprime.astro @@ -8,7 +8,7 @@ const crumbs = [ { label: 'Core runtime', href: '/core/quorum-crate/' }, { label: 'F´ components' }, ]; -const repo = 'https://github.com/mruspace/flight/blob/v0.6.0'; +const repo = 'https://github.com/mruspace/flight/blob/v0.7.0'; ---The source is in fprime/ of mruspace/flight. The requirements and the design were @@ -229,6 +229,13 @@ const repo = 'https://github.com/mruspace/flight/blob/v0.6.0'; from the state file after a kill, and 1.2% to 1.5% CPU in the timed run. It has not run on the SEPP. See{' '} the operations note.
+
+ A second deployment puts each replica in a process of its own: MruQuorum, the manager process, starts
+ three MruReplica processes, linked through F´'s GenericHub over Unix socket pairs (no
+ network), and pins them to the SEPP's two cores. The kill is real: the manager sends SIGKILL to a replica
+ process at the start of a cycle. In ESA's environment under emulation it gave the same counts and events as
+ the first deployment, with the three processes pinned in every segment. It has not run on the SEPP.
+
On one processor the manager and the replicas share the processor. A manager that falls behind used to close cycles before their answers were dispatched, so healthy replicas looked silent and were retired as lost. Since @@ -301,7 +308,7 @@ void quorum_health_clear(quorum_health *health, uint32_t replica);