-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TensorAlgebra] [Feature request] TensorAlgebra.contract to accept biperm #1507
Comments
I agree it makes sense to support the syntax: contract(((1, 4), (3,)), ft1, (1, 2), ft2, (2, 3, 4)) to specify which dimensions will become the codomain and domain of the output tensor, good suggestion. However, I think in terms of terminology you might be conflating the concept of labels and permutations, I don't think that supporting I believe the permutation version of that contraction would be something like: contract(blockedperm((1, 3), (2,)), ft1, blockedperm((1,), (2,)), ft2, blockedperm((1,), (2, 3))) I'm not sure if I got that exactly right but hopefully you get the idea. I'm not sure if that syntax is supported right now but if it isn't we should add it as well. |
For a
FusionTensor
, a permutation is not enough to specify the structure, a biperm is needed. Currently,TensorAlgebra.contract
does not allow this.Note that it is not possible to construct a
BlockedPermutation
from((1,4), (3,))
:but even a correct
BlockedPermutation
fails:The text was updated successfully, but these errors were encountered: