When the tensors to be contracted are matrices, the generated tasks are executed in parallel, and the total number of tasks makes sense (first image). The problem arises when the tensors to be contracted are of higher order, as EinCode starts to perform permutations in the dimensions and reshapes to carry out the contraction, seemingly generating an endless number of tasks (second image, and it hasn't even reached the end of the contraction). In the case where the tensors were matrices, these operations are not necessary, and the contraction operation is merely the matrix product, yielding the expected result.
When the tensors to be contracted are matrices, the generated tasks are executed in parallel, and the total number of tasks makes sense (first image). The problem arises when the tensors to be contracted are of higher order, as EinCode starts to perform permutations in the dimensions and reshapes to carry out the contraction, seemingly generating an endless number of tasks (second image, and it hasn't even reached the end of the contraction). In the case where the tensors were matrices, these operations are not necessary, and the contraction operation is merely the matrix product, yielding the expected result.