docs(perception): record Rerun projection acceptance

This commit is contained in:
DCCONSTRUCTIONS
2026-07-19 17:39:28 +03:00
parent 2b53168149
commit ada2a55ee6
6 changed files with 84 additions and 27 deletions
+28 -6
View File
@@ -9,7 +9,7 @@ K1
-> bounded missioncore.compute-job/v1
-> replaceable GPU worker / Triton
-> content-addressed missioncore.compute-result/v1
-> future optional Rerun derived layer
-> optional validated Rerun derived layer
```
The GPU worker cannot discover, provision, start or stop a K1. It receives an
@@ -61,6 +61,29 @@ The result manifest binds the detection artifact's length and SHA-256. A repeat
with the same identity validates the existing directory and returns it without
calling Triton.
## Recorded Rerun projection
Mission Core discovers only results whose validated job names the opened
session. Before projection it revalidates the complete job/result binding,
artifact digests, ordered timestamps and result metrics. It then reconstructs
the exact fMP4 epoch, verifies decoded dimensions/frame count with `ffprobe`,
decodes exactly the admitted number of RGB frames and rejects boxes outside the
image.
The optional `perception.rrd` endpoint returns either HTTP 204 or one complete,
bounded RRF2 stream for the opened Rerun recording ID. The browser never splits
that stream and never replaces the base recording when the optional layer is
absent or rejected. Accepted frames are logged under `/perception/camera` on
the canonical zero-based `session_time` timeline; `Image` and `Boxes2D` rows
therefore seek with the point-cloud archive. Generated overlays are a private,
content-addressed cache and remain rebuildable from the immutable job/result.
In **Наблюдение → Пространственная сцена**, a **Распознавание** button appears
only after the layer has been admitted. It switches the active native Rerun view
between the camera/detections and the point cloud. TEST007's accepted fragment
occupies approximately `01:07.351–01:12.848`; Rerun's latest-at query retains
the last admitted frame after that short fragment.
## Accepted model profile
- YOLOX-S official ONNX from upstream release `0.1.1rc0`;
@@ -76,10 +99,9 @@ accepted for obstacle avoidance, free-space estimation or safety decisions.
## Open gates
1. Import the accepted result as an optional session-timestamped Rerun layer.
2. Qualify TEST007's 206-second epoch and record throughput/resource telemetry.
3. Replace SSH/SCP with a reviewed authenticated worker transport.
4. Add bounded live queues, sampling/drop policy and acquisition-isolation
1. Qualify TEST007's 206-second epoch and record throughput/resource telemetry.
2. Replace SSH/SCP with a reviewed authenticated worker transport.
3. Add bounded live queues, sampling/drop policy and acquisition-isolation
tests.
5. Introduce tracking, segmentation/free-space, calibration and point-cloud
4. Introduce tracking, segmentation/free-space, calibration and point-cloud
models as separate versioned pipelines.