fix(observation): admit bounded LAB chunk coverage
This commit is contained in:
@@ -222,8 +222,41 @@ The 144.54-second step is viewer-container publication from already computed
|
||||
results, not detector, semantic or fusion inference. It is completed before
|
||||
operator handoff. Warm UI openings reuse the resulting 7,882,010-byte Rerun
|
||||
overlay. The synchronized base recording contains exact range markers, so the
|
||||
host timeline is a 59.962-second comparison window and cannot advance into a
|
||||
static post-E21 tail.
|
||||
host timeline is intended to be a 59.962-second comparison window and cannot
|
||||
advance into a static post-E21 tail.
|
||||
|
||||
### Operator admission regression and repair
|
||||
|
||||
The first E21.3 browser handoff exposed one additional boundary condition.
|
||||
Rerun `rrd split` preserves complete Arrow chunks so that all split outputs
|
||||
still sum to the source recording. The verified bounded RRD therefore contains
|
||||
a leading boundary chunk beginning at 34.756228209 seconds even though its
|
||||
declared operator window begins at 35.421857292 seconds. Its final timestamp is
|
||||
the declared 95.383857292 seconds.
|
||||
|
||||
The original browser admission gate required both decoded endpoints to equal
|
||||
the declared endpoints within 1 ms. Download and decode consequently reached
|
||||
100%, but the scene could never be admitted because the harmless 665.629 ms
|
||||
leading chunk spill failed the start equality check.
|
||||
|
||||
The repaired contract admits a digest-verified RRD when its decoded range
|
||||
*covers* the declared window. The host timeline and playback controller are
|
||||
then clamped to the declared 35.421857292–95.383857292-second window, and
|
||||
autoplay starts at the declared boundary rather than at the preserved chunk
|
||||
edge. Missing coverage at either boundary still fails closed.
|
||||
|
||||
Browser acceptance on the production build at `127.0.0.1:8000`:
|
||||
|
||||
- three clean catalog-to-E21.3 openings completed;
|
||||
- the second and third openings reached `Визуализатор готов` in about 0.5 s;
|
||||
- no opening remained at `Загрузка и декодирование · 100%`;
|
||||
- the operator timeline was exactly `00:00.000 / 00:59.962`;
|
||||
- 2D objects, segmentation and 3D cuboids were enabled together and rendered
|
||||
in the synchronized composition;
|
||||
- camera/AI presentation changed while playback advanced;
|
||||
- browser console errors after all three openings: 0;
|
||||
- frontend unit tests: 151 / 151 passed; TypeScript check and production build
|
||||
passed.
|
||||
|
||||
## Evidence
|
||||
|
||||
|
||||
Reference in New Issue
Block a user