[FEATURE] Sequential model - #323
Merged
Merged
Conversation
This was referenced Aug 22, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Sequentialmodel loading and processing through the normal Core model factoryconfig.models, with an empty top-levelweightsarray and the existing file versionCompatibility note
This does not change the existing
.namfile version. Earlier experimental Sequential exports that stored bare child configs plus flattened wrapper weights are intentionally unsupported because they do not contain enough information to recover child architectures and weight boundaries reliably.This PR also leaves the existing Core
Lineartap-order convention unchanged. Trainer/Core agreement for multi-tap Linear models is a separate compatibility concern and is not silently folded into Sequential support.Resolves #142