Initial changes to enable TP elements to pass through xform chain #6
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
Co-authored-by: Matthew Smith <mjsmith6@illinois.edu>
* Performs Loop Fusion * Performs Array contraction * Splits kernels at the granularity of fused einsums * Transforms those einsums using recorded values from github.com/kaushikcfd/feinsum Co-authored-by: Matthias Diener <mdiener@illinois.edu> Co-authored-by: Matthew Smith <mjsmith6@illinois.edu>
more verbose debug
Remove calls to `Einsum.__init__`
… into add-tensor-product-functionality
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Depends on:
pytoolsbranch: https://github.com/a-alveyblanc/pytools/tree/tag-propagation-ceesdillinois-ceesd/pytatodraft PR: New branch for TP axis tag testing pytato#5illinois-ceesd/grudgedraft PR: Tensor product axis tags grudge#4The branches above are different from the branches the PRs into main are based on. This is so that any changes that happen during the review process are guaranteed not to break what I've observed to work (not that I expect any breaking changes, but you never know).
Marking this PR as a draft since it depends on the branches mentioned above. My suggestion would be to hold off on merging this and the other draft PRs until the
pytoolswork is merged.