Skip to content
This repository has been archived by the owner on Dec 7, 2021. It is now read-only.

Think about the names of sparse storage types/tensors #10

Open
mtfishman opened this issue May 18, 2020 · 1 comment
Open

Think about the names of sparse storage types/tensors #10

mtfishman opened this issue May 18, 2020 · 1 comment

Comments

@mtfishman
Copy link
Member

It may be good to rethink the names of the sparse storage tensors and constructors. Right now there is:

  • Dense
  • Diag
  • BlockSparse
  • DiagBlockSparse

DiagBlockSparse may not be a good name, however. I think it is a bit misleading, because naively one might expect that it has a general block sparse structure (where any blocks may be nonzero), where the blocks are diagonal. However, it is actually a block diagonal tensor (the only nonzero blocks are along the diagonal), where the nonzero blocks themselves are diagonal. Therefore, it may be better to call it DiagBlockDiag. This looks like a strange name, but it is anticipating that we may want to have a BlockDiag storage where the diagonal blocks are dense (many block diagonal matrices already show up in the code, for example as inputs to eigen).

Additionally, we may want to rename these constructors:

to explicitly use UniformDiag instead of Diag, so it is clearer that a uniform Diag storage is being made.

@emstoudenmire
Copy link
Contributor

I agree: good to think about naming conventions that will "scale" to future designs we want to have.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants