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

re: measure the CAPTURE-axis noise floor -- 0 in-box, and the era result survives

Browse Source 
sylpheed-port found their main_menu row drifting 13.25-13.30 across runs on a
free-running spin clock, and made the general point that a margin only means
something against the noise it sits on. My --at plateau measures the RENDER axis;
it says nothing about how much the score moves between two CAPTURES of the same
screen, which is what a single JP grab is exposed to.

Measured from two independent captures of the settled EN title at different
phases of its free-running plate pulse, scored against one render:

  whole frame     peak 31.302  trough 28.463   spread 2.839
  inside the box  peak 21.230  trough 21.230   spread 0.000

The zero carries its control: the two captures differ by 83 496 px whole-frame
(max |d| 174), so they are genuinely different grabs, and by 0 inside the box --
the screen's free-running element is the plate, which lies outside the logo
region the adjudication uses.

Margins re-stated: stale-vs-fixed 16.7 is 14x the render noise and >=5.9x the
whole-frame capture noise, so the era result survives on both axes. And the
settle-vs-rest negative is STRONGER than first stated: 1.5 is not merely inside
the render plateau's 1.2 flatness, it is below the whole-frame capture spread of
2.8 as well.

Reach recorded: this transfers the EN title's capture noise to the JP title's
box, and build 7 carries ptloop01/02.rat which may animate inside that region
where the EN plate does not. A second JP capture would settle it and has not been
taken.

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-30 15:17:22 +00:00
parent a354025363
commit 93a587b7c0
1 changed files with 40 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
docs/re/structures/ui-resting-pose.md
View File

@@ -70,6 +70,46 @@ and there are two independent reasons:
produce a sharp minimum instead. The sweep was run for a noise scale and answers
this too.
### ✅ The CAPTURE axis has a noise floor too, and it is 0 in the region measured
`sylpheed-port` found their `main_menu` row drifting 13.25–13.30 across runs — a
focus ring spinning on a free-running clock — and made the general point that **a
margin only means something against the noise it sits on**. The `--at` plateau
above measures the *render* axis. It says nothing about how much the score moves
between two **captures** of the same screen, which is a second noise source and
the one my single JP grab is exposed to.
Measured, from two independent captures of the settled EN title taken at
different phases of its free-running plate pulse, scored against one render:
| | whole frame | inside the measurement box |
|---|---|---|
| plate-pulse **peak** | 31.302 | 21.230 |
| plate-pulse **trough** | 28.463 | 21.230 |
| **spread** | **2.839** | **0.000** |
⚠️ A 0.000 is the result this corpus distrusts most, so it carries its control:
the two captures differ by **83 496 pixels** whole-frame (max |d| 174) — they are
genuinely different grabs — and by **0** inside the box. The screen's free-running
element is the plate, which lies outside the logo region the adjudication uses.
**So the margins re-stated against every noise floor now measured:**
| comparison | margin | vs render noise (1.2) | vs capture noise (0.0 in-box, 2.8 whole-frame) |
|---|---|---|---|
| stale vs fixed era | **16.7** | 14× | ≥5.9× |
| settle vs rest | **1.5** | 1.2× | below whole-frame noise |
The era result survives on both axes. The settle-vs-rest negative is **stronger**
than first stated: 1.5 is not merely inside the render plateau's flatness, it is
below the whole-frame capture spread as well.
⚠️ **Reach of the transfer.** This is the *EN* title's capture noise applied to the
*JP* title's box. Build 7 carries `ptloop01/02.rat`, which may animate inside that
region where the EN plate does not — so the in-box 0.000 is a measurement on a
neighbouring screen, not on the one adjudicated. A second JP capture would settle
it and has not been taken.
⚠️ **Reach.** One screen, one capture. The absolute residual is ~40 RMSE even at
the best instant, because the JP title carries live animation a static render
cannot reproduce; every comparison here is relative and none of it says our render