Repository navigation
Support GradedArrays 0.17 and show an index's space - #268
Merged
Merged
Conversation
Member
|
Your PR no longer requires formatting changes. Thank you for your contribution! |
mtfishman
changed the title
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #268 +/- ##
==========================================
+ Coverage 78.00% 78.13% +0.13%
==========================================
Files 30 30
Lines 1823 1834 +11
==========================================
+ Hits 1422 1433 +11
Misses 401 401
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
mtfishman
force-pushed
the
mf/gradedarrays-0.17
branch
from
October 2, 2026 01:32
6fda647 to
322f36f
Compare
mtfishman
changed the title
mtfishman
marked this pull request as ready for review
October 2, 2026 17:00
mtfishman
enabled auto-merge (squash)
October 2, 2026 17:08
mtfishman
disabled auto-merge
October 2, 2026 17:22
GradedArrays replaced `SectorRange` with its own `Sector`, so the flux constructors here dispatch on that instead. Both sector types are spelled qualified, since GradedArrays and TensorKitSectors each define a `Sector`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
`GradedArrays` is a weak dependency at the root, and Pkg rejects a `[sources]` entry for a package that is not in `deps` or `extras`, so the pin made the whole project fail to resolve. It is a real dependency of the test project, which is where it belongs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
An `Index` printed only `length=N`, which gave a graded index no way to show its sectors or which way its arrow points. It now prints the space, and a tensor's summary line asks for the compact form and keeps the length so that one entry per leg stays readable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Covers building an `Index` from sector pairs, turning it around with `dual` or `conj`, and reading a tensor's arrows off its legs. The symmetries themselves are GradedArrays', so the page links into its docs for the list rather than restating it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
An index built as `Index(2)` stores a `Base.OneTo` and printed as `Index(1:2|id=...)`, which is neither how it was written nor how anyone would write it. It now shows the length, and an index over an explicit range still shows that range. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The page opened on duality, which a reader reaches for only once they have a tensor to apply it to. It now starts from graded indices and the array constructors, then contraction, scaling and addition, and keeps duality and the available symmetries for after. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Introduces duality through what contracts with what, and points at the graded arrays page rather than one section of it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Dropping GradedArrays 0.16 from compat is breaking, and main has since released 0.15.2. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Adds `from_range`, the inverse of `to_range`, so a graded index shows its `sector => multiplicity` pairs instead of the `gradedrange` call that built the range. The test files that pulled `names` into scope now qualify it, since shadowing `Base.names` broke any file included after them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
`dual(Index(...))` is the call that makes it, where a `dual` around the space is not a call at all once the space is a vector of pairs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Also points the TensorKit link at the repository's current location. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
GradedArrays 0.17.0 is registered, so test/ and docs/ resolve it from the registry. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
mtfishman
force-pushed
the
mf/gradedarrays-0.17
branch
from
October 2, 2026 21:50
803c087 to
8cae596
Compare
Raising the GradedArrays compat floor does not change ITensorBase's own surface, so this follows the breaking upstream as an ordinary patch. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
mtfishman
added a commit
to ITensor/ITensorNetworksNext.jl
that referenced
this pull request
Oct 3, 2026
## Summary Bumps compat to ITensorBase 0.15.4, the first release that admits GradedArrays 0.17 (ITensor/ITensorBase.jl#268). ITensorNetworksNext only uses `U1`, `gradedrange` and `isdual` from GradedArrays, so this is compat only. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
jack-dunham
pushed a commit
to jack-dunham/ITensorNetworksNext.jl
that referenced
this pull request
Oct 6, 2026
Bumps compat to ITensorBase 0.15.4, the first release that admits GradedArrays 0.17 (ITensor/ITensorBase.jl#268). ITensorNetworksNext only uses `U1`, `gradedrange` and `isdual` from GradedArrays, so this is compat only. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
jack-dunham
pushed a commit
to jack-dunham/ITensorNetworksNext.jl
that referenced
this pull request
Oct 7, 2026
Bumps compat to ITensorBase 0.15.4, the first release that admits GradedArrays 0.17 (ITensor/ITensorBase.jl#268). ITensorNetworksNext only uses `U1`, `gradedrange` and `isdual` from GradedArrays, so this is compat only. Co-authored-by: Claude Opus 5 (1M context) <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
2 participants
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.
Summary
Bumps compat to GradedArrays 0.17 (ITensor/GradedArrays.jl#285). An
Indexnow prints the space it was written with, so a graded one shows itssector => multiplicitypairs and its arrow, and there is a new docs page on building symmetric tensors.