Inconsistent DirectSolver interface.
未关闭
@yangcal 已经在做这个了。
开始于 2026年2月18日。
- 主要语言
- Cython
- 星标
- 601
- 派生
- 46
- PR 合并指标
- 30 天内没有已合并 PR
描述
Hi everyone! I've noticed a small inconsistency in the sparse solver interface, namely when it comes to using it with a 2D tensor where the last dimension is 1.
Given a 3x3 lhs sparse matrix and a 3x2 rhs dense matrix:
a = torch.sparse_coo_tensor([[0, 1, 2], [0, 1, 2]], [1.0, 1.0, 1.0], device="cuda").to_sparse_csr()
b = torch.randn([3, 2], device="cuda")
we can set up a solver for with:
nvsparse.DirectSolver(a, b.mT.contiguous().mT)
This works fine. However, for a 3x1 rhs:
b = torch.randn([3,1], device="cuda")
setting up the solver in the same way breaks with:
TypeError("The RHS tensor([[1.],\n [1.],\n [1.]], device='cuda:0') must be a matrix or vector with col-major layout, and for implicitly-batched RHS (N-D >= 3), each matrix sample must have col-major layout (the second dimension from the end must have unit stride.")
It would be great not to have to special-case this.
Best,
Ana
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
评估
这个 Issue 还没有评估数据。