Add TambaraYamagami for ZN - #110
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests.
🚀 New features to boost your workflow:
|
lkdvos
reviewed
Sep 16, 2026
lkdvos
left a comment
Member
There was a problem hiding this comment.
Looks great!
Left some small suggestions in the code, but I think everything looks more or less perfect.
Additional questions:
- Does it make sense to define
moduluslike we do forZNto return the value ofN, to avoid having to access the type parameters? - Do you have time to also include a documentation section for this, even if it is somewhat terse?
- Are there certain versions that you imagine using somewhat often, for which it makes sense to add them to the precompilation list here:
TensorKitSectors.jl/src/TensorKitSectors.jl
Lines 92 to 96 in 09e76e6
The show method used an invalid `<:TambaraYamagami` expression and always printed the placeholder "(:m)" regardless of whether the sector was the non-invertible object. It now mirrors the printing convention used by other sector types (skips the type name inside an already-typed context) and distinguishes `m` from group elements via `_ism`, producing output that round-trips through `Meta.parse`. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ince this fusion category is neither an anyon theory (as it is not even braided) or a (representation category of a) group.
Contributor
Author
|
Implemented almost all the suggested changes for now, except the |
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Jutho
reviewed
Sep 17, 2026
Co-authored-by: Lukas Devos <ldevos98@gmail.com>
…d to correctly deal with the case of the identity object.
lkdvos
reviewed
Sep 21, 2026
Co-authored-by: Lukas Devos <ldevos98@gmail.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… label cutoff Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
lkdvos
enabled auto-merge (squash)
October 1, 2026 14:54
lkdvos
disabled auto-merge
October 1, 2026 16:59
Merged
lkdvos
referenced
this pull request
Oct 1, 2026
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I added a new sector representing the Tambara-Yamagami fusion category with underlying abelian group$$\mathbb Z_N$$ . The implemented fusion rules and F-symbols are known analytically in the literature.
I have made the following choices
TambaraYamagami, and the underlying groupTambaraYamagami{2,1}, should correspond toIsingAnyon. I did not check this explicitly, but it passes all the tests. However,TambaraYamagami{2,1}in its current implementation is not endowed with a braiding, since this is the only