dummy-link

SparseWrappers

sandbox to improve operations of linear algebra wrapping abstract matrices

Readme

SparseWrappers.jl

sandbox to improve operations of linear algebra wrapping abstract matrices

There are some Wrappert types, which provide a specialized view to an arbitrary AbstractMatrix. There are at least two important aspects that justify their existence

  1. Storage space economy
  2. Specialization of algorithms applied on them

The existing wrappers of that kind are

No Wrapper class extra method
1. UpperTriangular -
2. LowerTriangular -
3. UnitUpperTriangular -
4. UnitLowerTriangular -
5. Symmetric(_, :U) -
6. Symmetric(_, :L) -
7. Hermitian(_, :U) -
8. Hermitian(_, :L) -
9. Transpose transpose
10. Adjoint adjoint
11. SubArray view

Items 1. - 4. have a common supertype LinearAlgebra.AbstractTriangular.

Items 5. - 6. and 7. - 8. share a common type, while their specialization to :U and :L is implemented by a data field uplo.

Items 1. - 8. have a common field data, which contains the referred abstract matrix. Items 9. - 11. use field parent to refer to the abstract matrix.

The types of all items are subtypes of AbstractMatrix. So it is possible to combine them arbitrarily. For example Symmetric(Hermitian(UnitUpperTriangular([3+im 4+im;5 6]), :U), :U) is a valid combination of wrappers. Intuitively, it should be equal to [3 4+im;4+im 6].

The ability to combine those wrappers liberately leads to an unlimited number of types, which makes it hard to design specialized algoritms for them, which are efficient.

This project was set up in order to improve this situation

Restrict Number of Types of Combinations of Wrappers
  1. Identify a small set of wrapped types, which can express all results of wrappers.
  2. Maybe additional types to be added to above list
  3. Maybe restrict support to "useful" combinations (is Hermitian(A) useful if diag(A) is not real?)
  4. provide extra methods for all wrappers, which produce output of limited set
Selected Operations for Wrapped Types
  1. sparse(A::X) for all wrapped types X should be as efficient as sparse(::Adjoint(SparseMatrixCSC))
  2. all unary and binary operations with wrapped types of sparse matrices should take advantage of the sparsity structure, as far as efficient
  3. if no specialized algorithms are availble, in the case of wrapped sparse matrices, the fallback should avoid the generic methods for AbstractMatrix, but use corresponding methods for AbstractSparseMatrix, after converting to SparseMatrixCSC.
Issues (an uncomplete list of unsolved problems - see combinitions.jl)
  1. Adjoint(Transpose(A)) == conj.(A)
  2. Hermitian(A) when diag(A) is not real: throw exception?
  3. Symmetric(Symmetric(A, :U), :L) should be Symmetric(A, :U)
  4. Symmetric(Hermitian(A, :U), :L) should be conj.Hermitian(A. :U)
  5. view(Symmetric(A), I, J) should be Symmetric(view(A, I, J)) if I==J, view(A, I, J) if I,J don't traverse diagonal, and fall back to sparse(view(Symmetric(A),I,J))) otherwise.
Factorization of wrapper combinations

All possible finite combinations of the existing wrappers form a finite set of operations. It is possible to transform all such combination to one of those 21. Nevertheless it seems not realistic to implement 21 special cases for all operations of wrapped sparse matrices. So in many cases, the fallback to one of the implemented special cases has to be organized.

Unitary Operations

Meaning: with one (wrapped) sparse argument.

No Name Description
U1 issparse determine if it is (indirectly) a wrapper of AbstractSparseMatrix
U2 sparse convert to SparseMatrixCSC
U3 iszero all elements zero
U4 norm LinearAlgebra standard function - vector norm of vectorized object
U5 opnorm LinearAlgebra standard function
U6 scalar multiplication
U7 multiply with dense or sparse vector

to be continued

Binary Operations
No Name Description
B1 == equality of 2 wrapped sparse matrices
B2 +,-,* arithmetic operations

to be continued

First Commit

09/25/2018

Last Touched

about 1 year ago

Commits

40 commits

Used By: