-
Notifications
You must be signed in to change notification settings - Fork 56
Change frobeniusschur factor #260
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #260 +/- ##
=======================================
Coverage 82.85% 82.85%
=======================================
Files 44 44
Lines 5757 5757
=======================================
Hits 4770 4770
Misses 987 987 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I am a bit confused; how did you find this one? This is unrelated to #245 , right? Since that would not be fixed by this extra |
|
This is indeed unrelated to that issue. We bumped into this because the A4 data does not respect this gauge choice, i.e. there we only have In particular, I found the following: using MultiTensorKit, TensorKit
AC = ones(ComplexF64, Vect[A4Object]((2, 6, 1) => 1) ⊗ Vect[A4Object]((6, 6, 4) => 1) ← Vect[A4Object]((2, 6, 2) => 1))
AC2 = fill!(repartition(AC, 3), 1)
AC2.data[2] = 0
t1 = copy(transpose(AC2', ((1,), (2, 3))))
t2 = transpose(copy(AC2'), ((1,), (2, 3)))In this case, I'm fine with making the choice of only supporting |
|
Ok, I agree that I have been using Maybe another question for @lalooten , it would be good to have a test case for all our functionality, and that could be treated as a sector with unique fusion, but that we then compare to the |
|
I don't mind either way, regauging such that the FS is always ±1 is not difficult, but on the other hand it if it does not impact efficiency it might be nice to allow it to be complex. Regarding a simple example, |
|
Yes, Z3 is what I thought. Can you remind me where to find the cocycle formula to use? |
|
For Z_n, the 3-cocycles are given here: https://mathoverflow.net/a/157012, might be worth it to just implement this for general |
|
Thanks; do you by any chance know if it still possible to give |
|
For general abelian groups with general 3-cocycles, this is not true; there is a 1-1 correspondence between braided fusion categories For |
|
No that is fine, I think I can go with |
|
I am going to merge this, as you are definitely correct that there needs to be a |
This is a small change that fixes some issues encountered with transposing and adjoints not commuting. We've traced the origin to being that while we aren't assuming the Frobenius Schur factor is +-1, we have no checks for that since for all our sectors this is true.
There is definitely a
conjmissing, and the one I added here seems to resolve the issue, but I absolutely did not think through whether or not it should be here, or here instead:https://github.com/Jutho/TensorKit.jl/blob/ef03d19f8add057074c8103470dc15d759e8cd43/src/fusiontrees/manipulations.jl#L309