Correlate infrastructure prelude classes by profile span
This commit is contained in:
parent
dfd3204e9a
commit
d998c08219
3 changed files with 387 additions and 0 deletions
|
|
@ -125,6 +125,12 @@ Working rule:
|
|||
looking for above the fixed rows?”; it is the narrower partitioning problem of how the observed
|
||||
`0x55f3`-to-next-`0x55f1` gaps divide between the two `0x52ebd0` flag bytes and the next
|
||||
record’s `u16 + byte` prelude.
|
||||
- The widened prelude correlation closes part of that partitioning too: grounded `q.gms` rows with
|
||||
a `0x03` post-profile gap now collapse cleanly to the next-record prelude pattern
|
||||
`0x0001 / 0xff` across `17/17` rows, while the zero-length class is a separate grounded outlier
|
||||
with dominant pattern `0x0055 / 0x00` across `18/18` rows and the `0x06` class remains the only
|
||||
large mixed frontier. So the next infrastructure slice should focus on classifying the mixed
|
||||
`0x06` rows, not on rediscovering the already-grounded pure-prelude `0x03` rows.
|
||||
- Reconstruct the save-side region record body on top of the newly corrected non-direct tagged
|
||||
region seam (`0x5209/0x520a/0x520b`, stride hint `0x06`, `Marker09` record stems) now that the
|
||||
`0x55f3` payload is known to be fully consumed by the embedded profile collection on grounded
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue