Repository navigation
Require explicit CPU backend qualification across structured solver methods - #214
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.
Baseline optional-backend skips did not establish the advertised method/backend capabilities. Required NumPy/JAX/CPU Torch jobs now explicitly import the selected backend and reject missing, empty, or skipped qualification. The Torch gate retains the previous complete-run contracts from #208.
A structured
(pool, group, trait)state with non-default-axis conservative transport checks all 13 deterministic fixed methods in float32/float64 against independent matrix-exponential trajectories and total-decay balances. Representative live/replay methods and JAX JIT/Torch functional AD are checked separately; SciPy sparse and unsupported BDF2/SDIRK scan configurations have explicit negative contracts. The published matrix separates value, AD, replay, host preprocessing, sparse, and CPU/GPU evidence.Closes #206.
Validation:
just format,just ci(818 core tests passed, 389 provider tests passed),just docs,just qualify(NumPy 40, JAX 48, Torch 65; zero selected skips), andjust build-allpassed. Installed core/provider wheels and strict typing/docs passed. GPU execution remains opt-in and unqualified by this CPU matrix; the new matrix qualifies existing algorithms rather than adding methods.