Add giant model summary command #46

New Issue

2026-08-13T15:08:04+02:00

lars commented

2026-08-13 15:08:04 +02:00

With conditioning types × type targets × generators × decoders × histories ×
router axes, the configuration space is well past what validate_config's
hand-written cross-checks can cover, and several combinations are silently
degenerate rather than rejected. A giant model summary --config config.toml
that builds the model with no data attached and prints the resolved graph —
per-module parameter counts, trunk in/out widths, which heads exist, and
which config keys were actually consumed — would make an invalid
combination obvious before a multi-hour run, and its consumed-keys half is the
runtime counterpart to the static consumed-keys audit test
(tests/test_config_consumed_keys.py).

Migrated from issues.md (v0.3.0 branch review, 2026-08-13), Issue 21.

With conditioning types × type targets × generators × decoders × histories × router axes, the configuration space is well past what `validate_config`'s hand-written cross-checks can cover, and several combinations are silently degenerate rather than rejected. A `giant model summary --config config.toml` that builds the model with no data attached and prints the resolved graph — per-module parameter counts, trunk in/out widths, which heads exist, and **which config keys were actually consumed** — would make an invalid combination obvious before a multi-hour run, and its consumed-keys half is the runtime counterpart to the static consumed-keys audit test (`tests/test_config_consumed_keys.py`). --- Migrated from `issues.md` (v0.3.0 branch review, 2026-08-13), Issue 21.

lars added the feature label 2026-08-13 15:08:04 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: lars/giant#46