Bugfix: add_entry! for PSparseMatrices #959
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Copied from GridapDistributed issue 138.
In Gridap, we declare the function
Algebra.add_entry
, which is used to assemble an(i,j,v)
triplet into different structures (counters, COOs and matrices). As usual, there are different specializations of this function. In particular, we have different functions forAbstractMatrix
andAbstractSparseMatrix
:As we can see, for
AbstractMatrix
we callcombine(aij,v)
whereas forAbstractSparseMatrix
we callcombine(v,aij)
. This leads to different behaviors whencombine
is not commutative. For instance,(a,b) -> a
would create different matrices depending on the type.