Replace the TensorOperations Optimal backend with OMEinsumContractionOrders ExhaustiveSearch#219
Merged
Merged
Conversation
mtfishman
force-pushed
the
mf/drop-tensoroperations
branch
from
6243767 to
03657ac
Compare
…onOrders `ExhaustiveSearch` Drops the TensorOperations dependency, which existed only to compute optimal contraction orders through the `Optimal` backend, in favor of OMEinsumContractionOrders' `ExhaustiveSearch` (added in TensorBFS/OMEinsumContractionOrders.jl#119, released in v1.3). `ExhaustiveSearch` is a port of the same `optimaltree` netcon algorithm, and ITensorBase's OMEinsumContractionOrders extension already dispatches on any `CodeOptimizer`, so no new code is needed. The `Optimal` evaluation-order algorithm is removed. Use `ExhaustiveSearch()` in its place. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mtfishman
force-pushed
the
mf/drop-tensoroperations
branch
from
03657ac to
92295e2
Compare
mtfishman
added a commit
to ITensor/ITensorNetworksNext.jl
that referenced
this pull request
Jul 13, 2026
## Summary Widens the ITensorBase compat to include 0.12. ITensorBase 0.12 removed the `Optimal` contraction-order backend (ITensor/ITensorBase.jl#219), so the `contract_network` test that exercised `ITensorBase.Optimal` now uses OMEinsumContractionOrders' `ExhaustiveSearch`, which runs the same netcon algorithm. This also drops the test's now-unused TensorOperations dependency. Co-authored-by: Claude Opus 4.8 (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
1 participant
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
Drops the TensorOperations dependency, which existed only to compute optimal contraction orders through the
Optimalbackend, in favor of OMEinsumContractionOrders'ExhaustiveSearch(added in TensorBFS/OMEinsumContractionOrders.jl#119, released in v1.3).ExhaustiveSearchis a port of the sameoptimaltreenetcon algorithm, and ITensorBase's OMEinsumContractionOrders extension already dispatches on anyCodeOptimizer, so it needs no new code. TheOptimalevaluation-order algorithm is removed. PassExhaustiveSearch()in its place.