Meta-ticket: Efficient numerical computations with tensor trains

[gh-honglizhaobob]

Following the progress with Ticket #30307, we propose to add computational functionalities with tensors via the tensor train decomposition, which is an idea originally named Matrix Product States in the quantum physics community and later popularized by Prof. Ivan Oseledets. As a computational tool, it represents tensors in compressed formats that would enable tensor operations with cost scaling only linearly in the number of dimensions.

• Affleck et al., Valence bond ground states in isotropic quantum antiferromagnets (​https://link.springer.com/article/10.1007/BF01218021)
• Oseledets, Tensor-Train Decomposition, SIAM J. Sci. Comput., 33(5), 2295–2317 (​https://epubs.siam.org/doi/abs/10.1137/090752286?journalCode=sjoce3).

This functionality is especially useful for high dimensional tasks to prevent the curse of dimensionality (such as in Riemannian optimization). Numerical packages are currently supported in MATLAB, Python, and C++. The MATLAB version is currently most versatile and robust.

We may consider internalizing this computational library for Sage, as an effort to formalize the currently available implementations. This addition can either be an additional child class under tensor, and overwrite the arithmetics; or a separate module. The backend is currently proposed to be tensorflow, however this may change / be flexible based on how the refactoring of Components progresses.

One can look at this github page for an example implementation in MATLAB (​https://github.com/oseledets/TT-Toolbox).

Ideally after the implementation of this ticket, users can specify a fixed rank tensor for a general manifold using tensor.modules, specify a ring and a frame, and perform useful and normally computationally intractable tasks using tensor train as a backend. Based on the progress of this ticket, one may also consider implementing other backends for storing a numerical tensor such as tensor rings and quantized tensor train.

For alternative tensor decomposition formats, please see the following survey papers:

• Tucker format: (Falcó, Hackbusch, Nouy, Tree-based tensor formats, ​https://arxiv.org/abs/1810.01262)
• Tensor ring: (​https://arxiv.org/abs/1807.02513)
• Quantized tensor train (see section 3.5.1): (​https://refubium.fu-berlin.de/handle/fub188/3366)

Tickets:

• #31998 Package ttpy (tensor trains)
• #31992 FiniteRankFreeModuleMorphism: Add method SVD (singular value decomposition)
• #31997 Topological tensor spaces (modules)
• #29619 tensors should have a sparse iterator
• #30373 Parent methods tensor vs. tensor_product
• #30235 Add construction methods to FiniteRankFreeModule and CombinatorialFreeModule
• #30309 Meta-ticket: Unify free module elements API: methods dict, monomial_coefficients, etc.
• #32034 Graphical representations of tensors

[mkoeppe]

Is ttpy still being maintained? I tried to install it (using sage -pip install ttpy) and ran into a Fortran issue:

    Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/COMPLEX(8)).
    tt/tt-fort/ort.f90:271:22:
    
      271 |    call dgemv('t',n,r,1.d0,yy,n,x,1, 0.d0,gv,1)

[mkoeppe]

(This is with gfortran 11.1 on macOS; this may be similar to the many issues that we had when gfortran 10 came along - #29456)

[gh-honglizhaobob]

Replying to mkoeppe:

(This is with gfortran 11.1 on macOS; this may be similar to the many issues that we had when gfortran 10 came along - #29456)

I didn't have an issue with downloading since I wasn't using pip but directly cloned the code on github. Based on their github's commit history it doesn't seem to be frequently maintained.. The MATLAB version is what I now use for my projects. I will update the MATLAB link in the ticket description.

[egourgoulhon]

Waouh! This looks promising!

[mkoeppe]

I have opened an upstream issue for the compilation errors: ​https://github.com/oseledets/ttpy/issues/82

[egourgoulhon]

Replying to egourgoulhon:

Waouh! This looks promising!

To make it clear: the above comment was about the ticket main goal and was not some ironical statement about the ttpy issue with gfortran ;-)

[gh-honglizhaobob]

slightly modified description