fabi/Syplheed-Reborn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

re: selection fixes are exhausted for the last 51 -- the correct block is not a candidate

Browse Source 
Implemented the proposed tiebreak as a last resort (take the attractor only if
nothing else validates), keyed first on "all coordinates multiples of 50" and
then on the sharper "all coordinates integral" -- the attractor reads
(42, -900, 2400), (-600, -500, -950) while real geometry carries fractions like
(24.55, 9.84, 4.46). Neither changed anything: still 51 inconsistent, 5480
decoded.

The null result is the finding. A mechanism that defers the attractor whenever
another candidate exists, and changes nothing, means no alternative candidate
validates for any of the 51: the correct block is not in the candidate list at
all. So the residual is not a selection problem and no reordering, scoring or
tiebreak will move it.

The frontier is vertex_run_starts -- the unit-normal run scan that builds the
candidate list -- which emits no start for these resources' real vertex buffers.

Both attempts reverted; only docs land here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Claude (auto-RE)
2026-08-12 00:57:09 +00:00
parent 343a26ecc0
commit 0f9c95c52e
1 changed files with 16 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
docs/re/structures/xbg7-mesh.md
View File

@@ -448,12 +448,22 @@ That also explains why the neighbourhood fix helped so broadly: it steers
resources away from a single strong attractor rather than resolving many resources away from a single strong attractor rather than resolving many
pairwise confusions. pairwise confusions.
🟡 **Candidate next step, with its risk stated:** reject (or de-prefer) a **Selection-based fixes are exhausted — tested.** The proposed tiebreak was
candidate whose sampled positions are *all* multiples of 50 with a large span — implemented as a *last resort* (accept the attractor only if nothing else
the attractor's signature. The risk is real: an earlier sweep for exactly that validates), first keyed on "all coordinates multiples of 50" and then on the
signature also flagged legitimate `e_rou_*` composite proxies, so it must be a sharper **"all coordinates integral"** — the attractor reads `(42, −900, 2400)`,
**tiebreak between validating candidates**, never an outright rejection, and it `(−600, −500, −950)` while real geometry carries fractions like
needs the same before/after gate (decoded must not fall from 5 480). `(24.55, 9.84, 4.46)`. **Neither changed anything: still 51.**
That null result is itself the answer. A mechanism that defers the attractor
whenever another candidate exists, changing nothing, means **no alternative
candidate validates for any of the 51** — the correct block is *not in the
candidate list at all*. Both attempts were reverted rather than kept.
So the residual is **not** a selection problem, and no reordering, scoring or
tiebreak will move it. The frontier is `vertex_run_starts` — the unit-normal
run scan that builds the candidate list — which does not emit a start for these
resources' real vertex buffers. That is where the remaining 51 live.
The ignored test The ignored test
[`mesh_consistency_disc.rs`](../../crates/sylpheed-formats/tests/mesh_consistency_disc.rs) [`mesh_consistency_disc.rs`](../../crates/sylpheed-formats/tests/mesh_consistency_disc.rs)