fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

re: reconcile the 49.6/92.3 split -- same numerator, and my explanation of it was wrong

Browse Source 
sylpheed-port reconciled the population gap exactly and I reproduced it: filtering
max_t > 0 gives 1781 records and 92.3 %, their figures precisely. Same numerator,
1643, both ways.

My stated explanation was wrong. I said the scan requires a timed keyframe; it does
not, because .max() returns Some(0) rather than None for records whose keyframes are
all at time 0, so 1530 records where the question has no content stayed in my
denominator and counted as failures by construction.

The conclusion is untouched -- +0x04 is 0 % under either denominator.

Records their diagnosis of why it stayed invisible: the numerator agreed to the
unit, so a shared 1643 read as agreement and neither of us looked there. And both
halves needed a qualifier neither carried -- 92.3 % is of the records where the
question is meaningful, not of nested records.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
This commit is contained in:
sylph-decoder
2026-08-31 03:57:21 +00:00
parent 73c2b31e1b
commit e6a9d372f3
3 changed files with 48 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
docs/re/structures/ui-record-loop-length.md
View File

@@ -22,10 +22,27 @@ disc-wide (1 781 records, 0 violations).
> a secondary statistic**: `+0x08` equals the largest keyframe time *exactly* in
> half the records and `+0x04` in **none**. No unrelated word reproduces that.
>
> ⚠️ My population differs from theirs — 3 311 records against 1 781, because this
> scan takes every pak and requires a timed keyframe — so the exact percentage
> moves (49.6 % vs 92.3 %). **The discrimination does not**: 0 % for `+0x04` under
> both counts. The consequence for the `PRESS Ⓐ` plate
> 🔴 **AND MY EXPLANATION OF THE 49.6 % WAS WRONG.** I wrote that my scan "requires
> a timed keyframe", so the population differed. It does not: `.max()` over the
> keyframe times returns `Some(0)` — not `None` — for a record whose keyframes are
> all at time 0, so those never left my denominator. `sylpheed-port` reconciled it
> exactly and I reproduced it:
>
> ```
> 1643 / 1781 = 92.3 % records where max t > 0 — the question is meaningful
> 1643 / 3311 = 49.6 % plus 1 530 records where max t == 0
> ```
>
> **Same numerator.** The 1 530 extra are records where *"does the word equal the
> largest keyframe time?"* has no content — `max t` is 0, so each counts as
> not-exact **by construction**. 49.6 % is not a weaker 92.3 %; it is 1 643
> successes over a denominator containing 1 530 questions that were never asked.
>
> ✅ **The conclusion is untouched**: `+0x04` is **0 %** under either denominator,
> so the offset stands on both scans.
>
> ⚠️ **And 92.3 % needs the qualifier it has never carried here**: it is *of the
> records where the question is meaningful*, not *of nested records*. The consequence for the `PRESS Ⓐ` plate
is then tested against the corpus's existing measurements of the running game,
which it passes and the previous reading fails.