Repository navigation
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
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.
For a square Kronecker product with rectangular factors,
diagonal()currently returns too few entries and incorrect values. The product of the factors' diagonals is valid when each factor is square, but not for rectangular factors whose product is square.Use the existing indexed diagonal implementation for nonempty products with rectangular factors, retaining the optimized path for square factors and the existing empty-product behavior. This does not materialize the full product. The regressions compare values and gradients against
torch.kron, including three factors, broadcast batches, and empty-product controls.Validation on Windows CPU, Python 3.12.14, PyTorch 2.14.1:
python -m unittest discover -qruns 5,049 tests. The remaining failure,test_psd_safe_cholesky_psd, also fails on the unchanged production baseline because the expectedNumericalWarningis absent. The full suite is not green.require-asciilauncher fails to resolve a Windows interpreter path. Running that same pinned ASCII-check script directly passes on both changed files.No CUDA, other-version matrix, or performance validation was run.