Repository navigation
Use valid einsum labels for Kronecker products with fourteen factors - #712
Open
austinchennn wants to merge 1 commit into
Open
austinchennn wants to merge 1 commit into
austinchennn wants to merge 1 commit into
Conversation
Author
|
@JeanKossaifi, could you or another maintainer please approve the first-contributor Test TensorLy and Lint with Black workflows and review this focused label-generation fix when convenient? Current head: |
3 of 5 tasks
This branch has not been deployed
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.
With the einsum tensor-algebra backend, a Kronecker product of14matrices fails because the equation builder walks past ASCII
zinto{and|. The core implementation succeeds on the same inputs, even when the result is only2x4.Generate labels from lowercase and uppercase ASCII letters. The contraction, final shape, ordering and backend operations are unchanged. Add one compact regression with14factors and a literal2x4expected result, using the existing numerical/tensor-algebra backend selection rather than an extra parameter grid.
Fixes #711.
Validation on CPU Python3.11 with the actual editable SDK:
tensorly/tenalg/tests: 360passed in each NumPy/PyTorch × core/einsum run,16warnings per run.black --check .:171Python files unchanged; notebook files skipped because Black's Jupyter extras are not installed.git diff --check:passed.Full repository,documentation,GPU and remaining numerical backends were not run. This repairs invalid labels within the backend's supported range; it does not remove einsum symbol/dimension limits or claim a performance improvement.
AI assistance:Codex investigated,implemented and ran the reported local checks with the account owner's authorization. The account owner has not personally reviewed or tested the patch. Please let me know if a different label-generation boundary would be preferable.