Repository navigation
Construct fusion tree blocks from the shorter side, and group the cached trees in fusionblocks - #581
Merged
Merged
Conversation
This was referenced Oct 14, 2026
lkdvos
reviewed
Oct 14, 2026
Codecov Report✅ All modified and coverable lines are covered by tests.
🚀 New features to boost your workflow:
|
lkdvos
reviewed
Oct 26, 2026
Member
Author
|
Done: the blocks now come in the order in which their uncoupled sectors first occur in The
|
lkdvos
approved these changes
Oct 28, 2026
Jutho
reviewed
Oct 28, 2026
Jutho
reviewed
Oct 28, 2026
For sectors with a simple unit, a superset of the coupled sectors suffices, as the fusion tree iterators yield nothing for the others: the unit if one side is empty, and otherwise the fusion product of the shorter side only, instead of the intersection of the fusion products of both sides. The trees and their order are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Instead of constructing a block for every combination of codomain and domain sectors, `fusionblocks` groups the cached `fusiontrees(W)` by their uncoupled sectors, in the same order as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`sort!(...; by = rank)` evaluated `rank`, and with it the `Dict` lookups of (product) sectors, at every comparison. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… only the longer side for trees Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…no legs on one side Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
For several units, a coupled sector of a block must be compatible with the units at both ends of either side; otherwise the fusion tree iterator throws instead of being empty. 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>
…ccur 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>
lkdvos
force-pushed
the
lb/fusiontreeblock_construction
branch
from
October 28, 2026 19:19
8e373fa to
3f74b72
Compare
lkdvos
approved these changes
Oct 28, 2026
lkdvos
enabled auto-merge (squash)
October 28, 2026 19:23
Jutho
approved these changes
Oct 28, 2026
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.
This is a draft illustrating some potential performance improvements; the actual implementations are
very much up for discussion.
Same blocks, same order, less work:
FusionTreeBlock{I}(uncoupled, isdual): forSimpleUnitsectors, the coupled sectors come fromthe fusion product of the shorter side only, instead of intersecting the products of both sides.
fusionblocks(W): groups the cachedfusiontrees(W)by uncoupled sectors, instead of constructinga (mostly empty) block for every combination of sectors.
New test: the blocks of a
HomSpacehold exactly its trees, in order.Cold construction of the recoupling data for one permutation of a tensor from a PEPS CTMRG step
(scripts below), main → this PR:
SU(2) gains little from threads:
FsymbolforSU2Irrepgoes through WignerSymbols, which takesa lock on every call. Removing that lock (caching the F-symbols in TensorKitSectors) is scheduled
as a follow-up.
TensorKit main (ae8abfc), SUNRepresentations c02a3f3, TensorKitSectors v0.3.10, Julia 1.12.5; shared 80-core
machine, two interleaved rounds agree within 15 %.
fℤ₂ × U(1) × SU(2) × U(1) reproducer (
julia -t8)fℤ₂ × U(1) × SU(3) reproducer (
julia -t8)🤖 Generated with Claude Code