-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How not to store 0's #110
Comments
No, this violates one of the core concepts of GraphBLAS: the pattern determines the sparsity not the operator/value. You can do GraphBLAS collections are not compressed over The original intent of GraphBLAS is to represent graphs, where it is perfectly reasonable for an edge to both exist and have a weight of |
@Wimmerer tnahk you for your answer. That's a shame, it makes a bit complicated what I'm trying to do. Although, I want to ask, it it possible to assign a GrB_NO_VALUE? For instance A[1,2] = GrB_NO_VALUE Thanks. |
You mean to delete that entry by assignment (or no-op if it doesn't exist)? Not in the current wrapper, I'll add that as soon as I get a chance. It will either be |
Note also this is the direction that many sparse libraries (potentially including SparseArrays.jl) are going in. The sparsity structure shouldn't necessarily be coupled to the fill. |
Hey @Wimmerer, I come back to ask you if you had a chance to implement the assignment deletion of a matrix entry. Best regards. |
Hi, given a sparse matrix
Note that it is stored in memory element [2,2] although it's 0. Is it possible to do
A[2,2] = 0.0
and make the matrix not store it?However, if A[2,2] were to be different from 0 and then I set it to zero, it will be important to store it as 0 so I can drop it later (or it should drop it automatically). After all, it's a space matrix, zeros should not be stored.
Thanks.
The text was updated successfully, but these errors were encountered: