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

re: pre-register the two-leaf period ratio before measuring

Browse Source 
pteff03a's declared timeline has never been checked against a capture. The
leaves declare 600 and 720 units, so the periods must differ by 1.200 within
a single capture. Equal periods is the flattering-but-wrong outcome the
batched-draw reading could have produced.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jc4pciRArGHfxGGhEbwp5t
This commit is contained in:
sylph-decoder
2026-09-03 19:22:37 +00:00
parent dfe21fda1f
commit 7c007cc421
1 changed files with 20 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/re/f6-two-leaf-periods-prereg.md Normal file
View File

@@ -0,0 +1,20 @@
# Pre-registration — the two sweeps must loop at 720:600
Committed **before** measuring. `pteff03a` was only found to be drawn at all in
[`f6-unit11`](f6-unit11-pteff03a-IS-drawn.md), so its declared timeline has never
been tested against a capture.
The leaves declare **different loop lengths**: `pteff03` **600 units**,
`pteff03a` **720**. If that decode is right the two strips must drift apart, with
> **period(pteff03a) / period(pteff03) = 720 / 600 = 1.200**
measured inside a single capture, so no clock or frame rate enters.
| if the decode is right | if it is wrong |
|---|---|
| ratio ≈ 1.20, in both captures | equal periods (one shared clock), or any other ratio |
Equal periods is the outcome that would flatter a lazy reading — one traveller
driving both quads — and it is exactly what unit 11's batched-draw discovery
could plausibly have produced. So the test can fail against me.