Skip to content

Converter data: preset-L map revision v1.1 (L's 13-entry dec0_values) - #116

Merged
phantoslayer21 merged 1 commit into
mainfrom
model-l/preset-l-map-v1-1
Nov 14, 2026
Merged

phantoslayer21 merged 1 commit into
mainfrom
model-l/preset-l-map-v1-1

Conversation

@phantoslayer21

Copy link
Copy Markdown
Owner

Model L (#89): the spec side's preset-L map revision v1.1 replaces v1 in data/preset-L.v1.map.json, byte for byte as
delivered. Compared with v1, three things change:

  • perm dec0_values is L's own 13-entry table [0, 1, 6, 7, 8, 9, 10, 11, 12, 2, 3, 4, 5]. Role order is A0, A1,
    A2, B0, B1, B2, Cx, Cy, Crho, latent candidate 0..3; role i reads decoder-block channel dec0_values[i]. L has no
    latent gate. v1 carried M's 17-entry table.
  • stage dec0's note says the same.
  • a top-level "preset": "L": the map names its preset (Converter: the map's preset by name (no change for M, K, F) #90's field).

No tensor reads the perm, so the converter's tensors and stage digests for L are unchanged. Only the map file's own
hash, recorded in a converted file's header, changes.

  • Same path, same loading. The file keeps its name, so every loader keeps working unchanged: the runtime's map
    name, test_l_runtime_load.py, and the converter tests. Without --preset the map now reads as preset L, since it
    names its preset. --preset L (Converter: the preset-L map, and --preset to name a map's preset #106) is still accepted, because it agrees with the field. Other presets are refused.
  • v1.1 has LF line endings, so tools/ci/check_line_endings.py drops the CR LF exception that v1 needed.
  • clean/converter/tests/run_tests.py test_l_real_map:
    • the map has "preset": "L", and dec0_values has 13 entries, a permutation of 0..12;
    • M's map keeps its 17;
    • preset L's message with and without --preset;
    • the same map without its key reads as version 1 (preset M's message);
    • the conversions in its exact layout as before.
  • clean/converter/README.md, data/README.md, the converter's usage text and a comment in map.h follow.

Not in this pull request: the reference table's own copy of the value positions (clean/l/reference/table.py
DEC0_VALUES, still M's 17 on main). The open Model L pull request that brings L's 13-entry table there mirrors this
map.

Refs #89

Tested

Local, Windows, CPU only, on main 72c32fc plus this commit:

  • Converter ctest (unit, decompression-vectors, synthetic, synthetic5): 4/4 passed.
  • run_tests.py: 5210 checks passed, 0 failed (5207 before; the new ones are the 13-entry table, M's 17 and the
    key-less map).
  • M, K and F outputs byte-identical: 1615 output files of the existing synthetic cases, SHA-256 identical to main's.
  • clean/l/runtime/tests/test_l_runtime_load.py (reads this map's stages, names, shapes and types): 5 tests OK.
  • python tools/ci/check_line_endings.py: 1175 files, 0 problems. Public gates (secrets, personal data, licence,
    chunks) pass.

Not tested

  • A real DLL; the packer and runtime reading the 13-entry table (their own pull requests); no GPU, no game.

… "preset": "L")

data/preset-L.v1.map.json now holds the spec side's revision v1.1, byte for byte:
perm dec0_values is L's own 13-entry table (L has no latent gate), stage dec0's
note is updated, and the map names its preset. No tensor reads the perm, so the
converted tensors and stage digests are unchanged. The file path stays, so every
loader keeps working; without --preset the map now reads as preset L. v1.1 has LF
endings, so the line-ending check's CR LF exception goes. Tests: the 13-entry
table, the messages with and without --preset; M's map keeps its 17 entries.

Refs #89

Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
@phantoslayer21
phantoslayer21 marked this pull request as ready for review November 14, 2026 00:59
@phantoslayer21
phantoslayer21 merged commit f15713d into main Nov 14, 2026
2 checks passed
@phantoslayer21
phantoslayer21 deleted the model-l/preset-l-map-v1-1 branch November 14, 2026 01:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant