ITensor / ITensor/ITensorNetworks.jl
Implement `inner`/`loginner` for TTN in terms of `contract`
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 128
- Forks
- 23
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 7
Description
I think ultimately inner/loginner for TT should just be designed based on calling a more general contract function with a contraction sequence appropriate for a tree network, and we can use a tree traversal as a way to quickly derive a reasonable sequence, and users can pass their own contraction sequence or function for computing a contraction sequence.
Originally posted by @mtfishman in https://github.com/mtfishman/ITensorNetworks.jl/pull/18#discussion_r1053673871
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing TTN inner and loginner behavior alongside the general contract API. Explore how a tree traversal can derive a contraction sequence, and define how callers can provide their own sequence or sequence-computing function; the work is done when both operations use this contract-based approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100