You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While updating SUNRepresentations to the latest version of TensorKit, I ran into an issue where it seems like the fusiontree iterator is generating trees that are not allowed. To reproduce this issue, running the tests for this branch does the trick, but the following also showcases the problem (using that branch):
I'm not 100% sure that the iterator is the culprit, but I checked with a couple versions of SUNRepresentations (specifically also before I changed the linear order) and the problem persists. The fusiontree iteration is definitely not something I am too familiar with though...
The text was updated successfully, but these errors were encountered:
This indeed seems to resolve the issues. I would suggest that we merge and tag this, then I'll tag the updated SUNRepresentations.jl version that depends only on TensorKitSectors.jl, which will make it easy to incorporate it in the tests here afterwards, without creating dependency cycles.
While updating SUNRepresentations to the latest version of TensorKit, I ran into an issue where it seems like the fusiontree iterator is generating trees that are not allowed. To reproduce this issue, running the tests for this branch does the trick, but the following also showcases the problem (using that branch):
I'm not 100% sure that the iterator is the culprit, but I checked with a couple versions of SUNRepresentations (specifically also before I changed the linear order) and the problem persists. The fusiontree iteration is definitely not something I am too familiar with though...
The text was updated successfully, but these errors were encountered: