Freeze independent DTW speech timing diagnostic and startup provenance

This commit is contained in:
karl committed 2026-10-13 18:33:21 +02:00
1 parent 705500425a
commit 3ac1201909
9 files changed
+250 -27

No files matched your search

+28
View File
@@ -89,3 +89,31 @@ Run only with the coordinator's available CPU inference slot. The previous
base-only run took about 251 seconds including decode/process startup. Token
alignment has not yet been timed; each ASR process retains the 600-second limit.
No production behavior or quality claim follows from structural tests.
## Separate DTW point-span comparison
`dtw-policy.json` freezes a separate base experiment. Replace `--token-sentences`
with `--dtw-sentences` and use a new output such as
`.searchi/speech/base-dtw-sentences-v1.json`. This adds `--dtw base
--no-flash-attn`: the pinned runtime disables DTW when flash attention is on.
Native `t_dtw` is a centisecond point, approximately the moment a token is output,
not a start/end interval. Multiply by ten; first and last ordinary-token points
define an approximate sentence point span. One-token sentences can have zero span.
Only source-window-bounded globally monotonic integer points are accepted.
Original ordinary interval errors are retained separately and never repaired.
Missing/invalid DTW points invalidate accepted scoring for the new comparison.
Frozen ordinary-v1 output remains failed and unchanged.
Pinned native default DTW graph workspace is 128 MiB; this is additional workspace,
not a total memory ceiling. Attention storage and disabled flash attention can
increase memory/time. Input remains 30 seconds, one CPU thread, 4 MiB output,
4096 tokens/segment and 600 seconds/process; observed peak memory/runtime must
be measured before production use. No inference has established this policy.
Future harness reports capture the executing-source SHA at startup and preload
alignment helpers before processing. The first ordinary-v1 run read its harness
SHA at completion while the on-disk harness had changed; that field cannot prove
the exact executing harness bytes. Its original raw token failures remain valid
diagnostic observations, and its excluded window already prohibits an accepted
quality score. Preserve that historical limitation instead of rewriting output.
References: pinned [token data/API](https://github.com/ggml-org/whisper.cpp/blob/d1be6fde11ac6e0407606b4e42fe72d34add8037/include/whisper.h)
and [DTW implementation](https://github.com/ggml-org/whisper.cpp/blob/d1be6fde11ac6e0407606b4e42fe72d34add8037/src/whisper.cpp).