Replace destructive setup with a reproducible CPU runtime and real model demo - #4
Merged
Merged
Conversation
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
1 participant
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.
The old installer deleted every .pkl file, changed system packages and regenerated requirements, while its dependency pins were incompatible. Replace it with an isolated Python 3.11 environment installer and compatible CPU wheels. Resolve baseline modules relative to the source file so they load outside the repository working directory.
Add a tiny framework/extension example that exercises the actual dataset, refined model and backward pass; run the installer and model regressions in CI. Rewrite the landing page around architecture, input contracts, runnable commands, citation and explicitly documented historical-artifact limitations.
Validation: 29 tests pass in the pinned CPU environment, including singleton/edgeless graphs, corrected labels, finite gradients and baseline loading. The installer preservation test checks that caches and requirements remain intact. Saved checkpoints/metrics still need regeneration after #2; follow-up tracked in #3.